What's the current state of jqMobi vs jQueryMobile? jqMobi's team has outlined issues with jQueryMobile[1]. What has changed since then? Does jqMobi have an edge?
[1] http://blog.jqmobi.com/post/15943804783/were-doing-it-wrong
[1] http://blog.jqmobi.com/post/15943804783/were-doing-it-wrong
My main question would be whether there is a long-term commitment to jqMobi by Intel. For something with Intel's name on it, the project pages have an embarrassing number of spelling and grammar errors. [1] I don't see a lot of contributors to the repo [2] and the unit tests haven't been updated in 3 months despite quite a bit of recent activity in the repo.
[1] http://app-framework-software.intel.com/
[2] https://github.com/01org/appframework
I'm the one responsible for all your complaints...sadly my dad is an edito, so I always feel bad with the spelling/grammar errors ;). You are correct in not every function works the same way (just as the case with Zepto.js). We've added new functionality and have even seen changes from our implementation make it's way into jQuery 2.0 (how props/attr work but not saying we are responsible)
For everyone else, Intel is committed to the project (that's about all I can say now). Keep a look out and you won't be disappointed!
Ian
As far as the attr/prop thing goes, we changed it a couple of years ago in jQuery 1.6 and deprecated the old behavior, but there is still a lot of code out there that does the wrong thing. That's why 1.9 was such a code breaker for a lot of people.
[1] https://github.com/01org/appframework/contributorsWould be nice to have some offline conversations - can you drop me a line? You can get my email from my github pages site.
thanks, Ian