Ext JS + jQTouch + Raphaël = Sencha
sencha.com
sencha.com
Sencha decided they couldn't build a sustainable business by continuing to not charge people for their hard work, a reasonable and dare I say responsible decision. People who are making money off their work now have the choice to financially support that work, rather than simply seeing it die completely, which is what would have otherwise happened.
http://groups.google.com/group/Google-Web-Toolkit/browse_thr...
It is not about the money. It is about changing the license after you've made a big commitment.
I just hope Raphael and jQTouch will continue to be developed independently.
I've been developing with it for a couple of years and am quite happy with performance. Of course its going to be sluggish if you're targeting ie6 or something since the DOM the framework creates is HUGE.
Would be nice if they ditched support for ie6 which would probably help a lot with DOM bloat.
I was continually frustrated until I finally settled down with a glass of hot chocolate, some romantic mood lighting, and started getting... intimate... with the source code. Even then, with GXT, it would be some nasty fights with a mediating debugger when it would stop talking to me and I had to pry out the reasons why. Usually, it was because some event wasn't being listened to.
A bad library is much like a bad relationship. When it's good, it's really good, but you forget that far too much.
The highlighted quote from Adobe.
The fact that Sencha is named "in the tradition of Java".
If you look at the front page, you easily tell that it isn't oriented toward developers. Contrast this with, for example, http://jqtouch.com/, http://jquery.com, and http://raphaeljs.com/
When you finally figure out where the API and demos are, it still takes quite a while to figure out if some jslib things are supported -- for example, some kind of rich text editor. I just looked again, and I don't think it is, but really I'm not sure.
I very well may try it, though. I've been looking for a project that makes a beautiful, cohesive interface, largely for web game programming purposes. I'm glad to hear that, despite its homepage, developers find it to be a nice project to use =)
I found that rather chilling, myself.
It's great though if that's what you want. Something which is actively developed, support to hunt down and solve gnarly JS bugs if you need it and the documentation is extensive and covers everything you'd want to know.
Each to their own I guess :)
Either way, jQTouch is an incredibly popular jQuery plugin - and since it's MIT licensed - we'll do everything we can to make sure that a copy that runs on jQuery will exist in the long term (either by providing an alternative set of tools or by making sure that a jQuery-using version of jQTouch has a good, well-maintained, home).
I seriously doubt that. jQuery UI is a hack compared to ExtJS.
Probably safe to say that he's no longer involved.
However, I cannot see a several megabyte framework [yes, it is: the ext js download is nearly 11MB, zipped(!!!)] working very well for mobile development.
ext-base.js and ext-all.js, minified, are fairly light.
Further, there's no ExtJS builder that I am aware of, so there are no optional "modules." I'm not sure what you're talking about. While the components are technically decoupled, using a GridPanel without Ext.data's offerings, for instance, would be pretty clunky.
Cappuccino's download, for example, comes with two complete versions of the code, plus the documentation, plus a sample app. And there's also a separate tools download. Hardly representative of anything at all.