Skip to main content

Microsofts First iPhone Application

On yet another occasion , software giant Microsoft has been extending its "coverage" on other platform. Just yesterday , they have release their first application to run on Apples iPhone (perhaps even on iPod Touch too). The Seadragon Mobile is a free image-browsing app that allows users to quickly "deep zoom" images while online and is intended to demonstrate what is possible with mobile platform.It is the backbone for Microsoft's Photosynth, which allows users to take a grouping of photographs and stitch them together into a faux 3D environment. an article from CNET news also mentioned that other iPhone apps are being developed at Microsofts Live Labs .

Some may welcome this move of the software giants to expand and penetrate the iPhone market, others may simply see it as another marketing strategy to display what they can do . when asked why they have the made the new application available to the iPhone first before their own mobile platform , they simply say :"The iPhone is the most widely distributed phone with a (graphics processing unit). Most phones out today don't have accelerated graphics in them. The iPhone does and so it enabled us to do something that has been previously difficult to do."

I appreciate Microsofts way of getting the best out of any available technology . They have the idea but Apple got the needed technology. Unselfishly , they decided to put it in Apple. I am not a Microsft guy or an Apple patron , I just like the way how technology is being used by anyone. I run Vista and Linux , I have an iPod and I use nokia phone so what the heck....
Labels:

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more