appframework

Hi Ian, I think you're doing an amazing job, but basically by yourself if the GitHub graphs are any indication [1]. It helps to have a group of people with differing experiences and perspectives when designing an API, and of course more people to do the heavy lifting as well. If docs aren't your thing, then there should be someone to review and write the docs. Since jqMobi has diverged from jQuery, that makes docs even more important because the name implies to people that it works like jQuery. 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/contributors

jqMobi and jQuery Mobile are two very different things. Despite "jq" in the name, jqMobi is not jQuery (or jQuery Mobile) compatible. It has a similar syntax and implements a subset of features, but even the APIs with the same names are not always fully compatible. 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 [Edit: I should say I'm on the jQuery team]

so this is jqMobi [ rebranded + extended ? ] github : https://github.com/01org/appframework/