The State of PhoneGap with Windows Mobile
So where does this leave PhoneGap WinMo? These are the ways we can proceed:
- Have a totally separate Js codebase, based on JScript 3, for WinMo. Con: Maintenance nightmare?
- Upgrade to IE Mobile 6. This discussion has its own section, below.
- Use WebKit with Qt . Pro: We can probably use Qt Webkit in Nokia phones (soon, not supported yet), because well, Nokia owns Qt. Con: Using Qt adds a 10MB overhead, minimum.
- Use our own WebKit control. Con: I don’t know how long this effort will take, and it is the riskiest.
Internet Explorer Mobile 6
Even if we somehow get IE Mobile 6 on existing phones (with unofficial ROMs, eg through xda forums), .NET code cannot take advantage of this, because Microsoft does not want to break existing compatibility with existing code that uses hosted controls .
 IE Mobile 6 release blog post http://blogs.msdn.com/windowsmobile/archive/2008/11/11/internet-explorer-mobile-6.aspx
 IE Mobile 6 will not be available for current phones http://blogs.msdn.com/windowsmobile/archive/2008/11/11/internet-explorer-mobile-6.aspx#9063740 [All comments were deleted after the fact by MS]
 IE Mobile 6 will not be available in hosted controls (ie .NET WebBrowser component) http://blogs.msdn.com/windowsmobile/archive/2008/11/11/internet-explorer-mobile-6.aspx#9064039[All comments were deleted after the fact by MS]