All fair comments. I fully realize jQuery
MOBILE has a focus on mobile devices :)
However, if you are tasked to write an app that runs on the desktop and on mobiles you can:
1. write two apps using two different frameworks, with different css, classes etc. Thats twice the amount of work.
or
2. use a single framework with minor adaptations for different form factors (for example tablets allow lists and drill-downs to be visible simultaneously etc.)
The early JQM
design sketches (well worth a look for their inspiring awesomeness) - lead me to believe the jQM team is aiming for just such cross browser, cross form factor (phone/tablet/desktop) capabilities in the future.
So now the question becomes, when does JQM actually become a deployable tool for such a desk+phone scenario ? My argument for giving IE8 compatibility (and I realize that is no trivial task) precedence over WinMo7 compatibility is that it would make the then existing jQM much more widely deployable. And not yet doing WinMo7 will hardly be noticed given the small installed base of that OS so far.
Also, wouldn't the task of supporting WinMo7 which has a truly ancient IE7 & IE8 codebase be HARDER than beginning with desktop IE8 ?? And on top of that, there is a rumor that MS realizes its WinMo7 browser is behind the curve and they may introduce a rev "Mango" based on the IE9 codebase later this year in which case the work to do WinMo7 first rel would go up in smoke.
Or perhaps my whole argument makes no sense since supporting the WinMo7 browser with its IE7/8 codebase is the bigger and harder task anyway and once that works, Desktop IE8 will automatically work also (I don't know) ?
Anyway, I am not sure its helpful or realistic ("cant make a baby in 1 month" etc.) but I am willing to vote with money not just words and put up a $2,000 incentive for JQM IE8 compatibility. I am a coder not a css/browser compatibility guru so I won't be much use hands-on but very willing to help test regularly.
jQM is still alpha and there is obviously a lot of work to be done, but I think it really has fantastic potential for single source web-application development (plus looking really good the more it converges on the
designs and capabilities mentioned above)
GO JQM !