Showing posts with label Windows Mobile. Show all posts
Showing posts with label Windows Mobile. Show all posts

Friday, December 31, 2010

Help for choosing a great #WindowsPhone7 device

This infographic put together by the folks at Technobolt allows you to quickly compare the important features of all the WP7 phones available, so that you can make the best choice based on your needs (Click to view it in its full glory):

I bought the Samsung focus based on its screen type (Super Amoled) and its weight and I love it!

Thursday, October 14, 2010

WP7–InputScopeValues and the key layouts

Screen shots of layouts of the different keypad layouts available on the WIndows Phone 7 (as taken from the emulator).

InputScopeValues - http://msdn.microsoft.com/en-us/library/system.windows.input.inputscopenamevalue.aspx

tip: If you want to start your app with the SIP keypad displayed, one easy method is to set focus on a text box on the page.

this.Loaded += 
new RoutedEventHandler((object sender, RoutedEventArgs e) => {txtBox.Focus();});
Default image
Url image
FullFilePath image
FilePath image
EmailUserName
EmailSmtpAddress
image
LogOnName image
PersonalFullName
PersonalNamePrefix
PersonalGivenName
PersonalMiddleName
PersonalSurName
PersonalNameSuffix
image
PostalCode
AddressStreet
image
AddressStateOrProvince
AddressCity
AddressCountryName
AddressCountyShortName
image
CurrenyAmountAndSymbol
CurrencyAmount
image
Date image
DateMonth
DateDay
DateYear
image
DateDay  
DateDayName image
Digits
Number
image
OneChar
Password
image
TelephoneNumber
TelephoneCountryCode
TelephoneAreaCode
TelephoneLocalNumber
image
Time
TimeHour
TimeMinorSec

image
NumberFullWidth
AlphanumericHalfWidth
AlphanumerFullWidth
image
Text
Chat
image
Search image
NameOrPhoneNumber image

Saturday, October 02, 2010

Windows Phone 7 Developer Launch Events

728x90_Banner_WP7DevLaunch

We had one in Denver September 25th. The next closest one is on October 12th in Colorado Springs. Find one nearest to you at: http://www.msdnevents.com/wp7devlaunch/

And even if you don’t have one that is occurring near you, there is one that will be simulcast – register at: https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032458870&EventCategory=2&culture=en-US&CountryCode=US

Disclaimer: this post enters me to win a free WP7 phone (link).

Monday, September 06, 2010

Ad–Windows Phone 7 is coming…

I am excited enough that even though I was eligible for an iPhone upgrade in july of this year, I plan to wait for the Windows Phone 7 launch later.

Tuesday, August 31, 2010

Windows Phone Developer Tools Beta (June) Install Issue

If you find that June 2010 installer for Windows Phone Developer Tools (beta) hangs while running imagegen.exe, then check to see if you have an AntiVirus application with AutoProtect features turned on. On my machine, it looked as though Norton AntiVirus’s auto-protect features was blocking imagegen.exe from completing on my machine.

Once I temporarily disabled Autoprotect, the installer ran successfully.

Saturday, May 01, 2010

Hello World – Windows Phone 7

image

Loading an image in SilverLight at run-time.

Drag an image control onto the design surface. Call it SampleImage.

if (Uri.IsWellFormedUriString(UrlTextBox.Text, UriKind.RelativeOrAbsolute))
{
BitmapImage bi = new BitmapImage();
bi.UriSource = new Uri(UrlTextBox.Text, UriKind.RelativeOrAbsolute);
SampleImage.Source = bi;
}

And here is a sample URL that you can use: http://bit.ly/dp9R26 (links to the Windows phone image shown above).

Saturday, March 20, 2010

Windows Phone Developer Tools CTP

http://www.microsoft.com/downloads/details.aspx?FamilyID=2338b5d1-79d8-46af-b828-380b0f854203&displaylang=en

What it includes:

Visual Studio 2010 Express for Windows Phone CTP
Windows Phone Emulator CTP
Silverlight for Windows Phone CTP
XNA 4.0 Game Studio CTP

note: requires a restart of the computer

Saturday, November 29, 2008

Nav N Go’s iGo – Light years ahead of competition

 iGO_My_way_8_Cockpit_n I first started using Nav N Go’s iGo software when it came packaged with the Mio c310s. The software runs on Windows mobile OS. The graphics were clean and clear. The interface simple and yet highly customizable. There were many websites dedicated to hacking the iGo software. The list of features that I liked are endless (smart zoom, quick overview of route, easy customization of route parameters, etc.) I loved the software very much.

Unfortunately, this year, not many of the low-end devices came packaged with the iGo 8. This new version is vastly improved (even better graphics, more options, 3D land-marks, etc) and I wish I could get my hands on a device that was cheap (under $200 or at least one to review). With none available and my c310 aging out, this year I begrudgingly, settled on a Garmin Nuvi 260.

But if you have the $ then check out this list of devices that run the iGo 8. The iGo8 will definitely not disappoint you.

Current list of devices supported by Nav N Go iGO 8:

Airis T482igo_8_pack
Airis T620
ASUS MyPal A686
ASUS MyPal A696
ASUS P320
ASUS P535
Dell Axim X51v
Eten Glofiish M700
Eten Glofiish M750
Eten Glofiish M810
Eten Glofiish X500
Fujitsu-Siemens Pocket LOOX 720
Fujitsu-Siemens Pocket LOOX N500
Fujitsu-Siemens Pocket LOOX N520
Gigabyte g-Smart i
HP iPAQ h2210
HP iPAQ h4150
HP iPAQ rw6815 Personal Messenger
HP iPAQ rx5940 Travel Companion
HTC Athena 100 (X7500)
HTC Pharos (P3470)
HTC Touch Cruise (P3650, Polaris)
HTC Touch Dual (20 key) 5520
HTC TyTn (P4500, Hermes 200)
HTC TyTN II (Kaiser)
MiTA  Mio 168
MiTAC Mio 169
MiTAC Mio 180
MiTAC Mio A501
MiTAC Mio A701
MiTAC Mio A702
MiTAC Mio P350
MiTAC Mio P360
MiTAC Mio P560
MyGuide 7500XL
Palm Treo 750
Samsung SGH-i780
Toshiba Portege G810
Yakumo deltaX 5 BT

And a much more detailed list after the jump (link).

My wife has the HTC tilt mobile phone and I am going to check out to see if I can get the iGo8 to run on it and review this latest version from Nav N Go.

GPS – Mio and Garmin 2008

miotm_rgb_logoI loved my Mio c310 portable navigation device (PND or is it personal navigation device, never mind!). I loved the fact that it ran Windows CE and the mapping software was iGo 2006. The combination of using Windows CE and iGo, provided for a device that had crisp and visually pleasing graphics and an interface that was highly customizable. The c310 had its quirks but at $150 in 2006, it was a steal of a deal and I never got lost. The iGo mapping software is the standard that I hold other PNDs to know.

The biggest problem with the Mio c310 that I had was that the company did not put out map updates often enough and their customer service kinda sucked (just check the number of people who commented on my posts on upgrading the map software and how they could not get any help from Mio and used my post to unbrick their 310s).

Mio with NavMan software (Moov series)So this year I started looking at the Mio’s Moov series of GPS. And boy was I disappointed to learn that they had replaced the iGO mapping platform with the software that used to run on the NavMan devices (I believe Mio acquired NavMan, which is why that is the software that is now packaged on these devices). Now there are a ton of people that think this was a good decision on Mio’s part as the NavMan is simpler to use with far fewer functions and is less customizable (read crippled!). This year Mio had the Moov 500 on sale at RadioShack for $150. With a wide screen layout and text-to-speech (TTS) it is the cheapest full featured GPS on the market. And I would have bought it, if only it had the iGo software running on it. From my very limited testing with the devices screwed down to the desk, I just did not feel like the NavMan software brought anything new to the party. I would have liked to test the device for a week and return it in a week if I didn’t like it, but given the state of the economy, I did not want to buy something that I might have to return and cause a company to take on a loss.

Garmin Nuvi 260So this year, after tons of research, I settled on the Garmin Nuvi 260. This device does not have a wide-screen, but it does have text to speech (which means spoken street names - “Turn right in 100 feet on to Lincoln street”, instead of “turn right in 100 feet”). In addition, Garmin has a good map update policy and you can generally buy new maps every year for around $70. Garmin Nuvi’s also support a browser plugin, that allows you to send locations directly from Google Maps to your device when it is connected to your computer.

My only problems with the Nuvi: The device runs Linux and the graphics are just not crisp. (I felt that was also the same problem that the TomTom’s had). In addition, as someone who loves to tinker with his devices, there are just about zero hacks for the Nuvi(s) (same is true for the TomTom). I just cannot customize the map screen to show me the details that I am interested in and I am stuck with what Garmin decided that I must see while I drive. (On the Mio, I could have current elevation, time to destination, distance to next turn, just about anything that could be computed could be put on the screen).

The pluses for the Nuvi are: Solid map update technology, so you wont need a PhD in computer science to update the device’s firmware or maps. Simple interface – you will never ever need to break out the manual. Has TTS on a low end model. 5 hours of battery – so you can take it out of the car and on your walks around the city.

 

list of my posts on the Mio - http://blog.aggregatedintelligence.com/search/label/Mio

list of my posts on GPS devices - http://blogsearch.google.com/blogsearch?hl=en&source=uds&q=GPS%20blogurl%3Ahttp%3A%2F%2Fblog.aggregatedintelligence.com%2F

Wednesday, February 06, 2008

Windows Mobile 6 Device Types - Smartphones & PDAs - What's the Difference?

Here is more information on the different flavors of WM6

wm6_naming_chart 

from: Windows Mobile 6 Device Types - Smartphones & PDAs - What's the Difference?

Different flavors of Windows Mobile 6

I recently began playing with the Windows Mobile 6 SDK and the first thing that you realize are there are 2 major flavors - Standard and Professional. Within these two flavors - there are more choices to make. Truly mind boggling!

Here is what I found from my research:

4 The first thing to realize is that there are 3 flavors of the devices that you can buy: Standard, Classic and Professional. Classic and Professional devices support touch screens, whereas Standard does not. If you wish to develop for the classic or the professional devices, then you need the professional version of the WM6 sdk.

The standard and professional devices are smartphones - support phone services as well as act as a PDA, the classic devices - are only PDAs. (If you are looking for a map from the old devices then basically the Windows Mobile for PocketPC platform is now the WM6 Classic platform and the old Smartphone platform is now the Standard and Professional WM6 platforms).

The good news is that even though there are two versions of the SDK, there is quite a large overlap over the libraries used and the installer created using any one of the SDKs can be used to deploy to all three types of devices.

Here is a summary of the different types of devices supported by the 2 versions of the SDK:

  • Windows Mobile 6 Standard SDK (does not support touch screens, but supports phones)
    • Windows Mobile 6 Standard (176x220 pixels - 96 dpi)
    • Windows Mobile 6 Standard Landscape QVGA (240x320 pixels - 131 dpi)
    • Windows Mobile 6 Standard QVGA (320x240 pixels - 131 dpi)
  • Windows Mobile 6 Professional SDK (supports touch screens - all versions except classic support phone services)
    • Windows Mobile 6 Classic (240x320 pixels - 96 dpi)
    • Windows Mobile 6 Professional (240x320 pixels - 96 dpi)
    • Windows Mobile 6 Professional Square (240x240 pixels - 96 dpi)
    • Windows Mobile 6 Professional Square QVGA (320x320 pixels - 128 dpi)
    • Windows Mobile 6 Professional Square VGA (480x480 pixels - 192 dpi)
    • Windows Mobile 6 Professional VGA (480x640 pixels - 192 dpi)

One can use either Visual Studio 2005 or 2008 for developing applications for WM6.

For code that will run on the device - there are two major ways in which you can create your applications:

  • Use native code for high performance, if you need direct hardware access, or if you require the smallest footprint. For native development, use Visual C++ to access Windows Mobile’s native APIs, as well as the Win32, ATL, and MFC frameworks.
  • Use managed code with the .NET Compact Framework for user interface-centric applications that require fast time-to-market or rapid application development. You should also use managed code if you want easy access to Web services or data held in SQL Server or SQL Server Compact Edition.  With .NET Compact Framework, you can use Visual Basic .NET or C# to access a healthy subset of the.NET Framework libraries.  Windows Mobile 6 ships with the .NET Compact Framework in ROM.
  • Useful links: