Windows Mobile Widgets are totally ridiculous
Wednesday, 28 October 2009
Today I read an article on the Window Mobile Development Blog that makes it difficult for me to take the whole widget standard seriously. And don’t get me started about Windows Mobile as a platform. One of the biggest advantages is also its biggest disadvantage: cross platform support.
The article is called Widget Anatomy – Touch and D-Pad inputs, oh joy! and I am still not sure if the title is meant sarcastically. It should be, although I fear it was meant seriously. The first example is how easy it is to use Touch from within your widget: you can just use the
onclick event handler. Sure, this is a good practice. Even the iPhone web browser does this. However I absolute do want a way to get the raw touch events from the phone. The
onclick event might be good enough for a simple webpage, but it surely isn’t for a widget that is supposed to work like a native app.
The next example is how to use the Directional Pad – the small button with four arrows that you used to use to navigate your phone before touch screens were invented. Well it is still an important way to navigate your Windows Mobile phone. The example tells us we can use this button to navigate between elements that have a
tabindex property and use the
:focus CSS selector for this purpose. Well… Yes, but not in Internet Explorer.
So writing widgets has become as frustrating as web development was before Internet Explorer 7 and 8 were released. At least for web development we now have something to look forward to. The death of Internet Explorer 6. The crapfest on mobile is just beginning…