Hi Bee, I nearly agree with you, but I think that qooxdoo needs:
1. Better Html editor (I'm using qooxdoo the long time and html editing simply does not I'm expecting to). 2. Upload widget integration 3. Better default theme. I like that qooxdoo goes its own way, but the Modern theme isn't really modern (to me) and Classic theme is hideous (mainly the hovering styles, see pushed buttons, focused list box, etc...). Here the ExtJS is clearly winner. 4. Finished databinding and unified programming style for all components. Working with table is really different to working with list, etc. I think that qooxdoo in future should contain only virtual-widgets (I'm sure that this is going to happen) and to optimize rendering and remove many DOM elements the <canvas> element will be used. 5. Better performance - qooxdoo is really slow compared to other toolkits. Just my ideas:) -- Best regards - Petr Kobalicek <http://kobalicek.com> On Fri, Jun 11, 2010 at 6:09 PM, Bee Jay <[email protected]> wrote: > Hi all, > > First of all, I thank this project for providing such a good framework. What > I'm about to say doesn't meant to question the effort of the core developers. > I believe they have been giving their best for this project. > > However, I feel the speed of the development of this project seems to be very > slow. Especially if I compare it with other similar well known frameworks for > RIA. While other frameworks had provided many advance features, controls, and > modern look, Qooxdoo still offers "standard" and "classic". For example: no > comet support, no charting, no REST support, less built-in theme options, > less rich widgets, no advance data store, no local storage support, no AIR > integration, etc. Ok, maybe I should mention my main reference of comparison: > ExtJS. > > I know Qooxdoo has better internal design and API, also better license. But > when its features can't fulfill the demand of most users, I'm afraid they > will leave Qooxdoo for better alternatives. On the other side, I know Qooxdoo > is being used by eyeOS project. When I tried eyeOS demo, I found they have > some advance widgets that are not provided by Qooxdoo itself. Can Qooxdoo > collaborate with eyeOS so we could have more advance controls so core Qooxdoo > developers could focus their work on the non-widget features? > > So, could we know what make the development so slow? What can we do to help > speed up the development? What kind of support that is needed by Qooxdoo from > us (the user of Qooxdoo)? > > I just want to see this project goes forward and become one of the best > framework for RIA, simply because I'm a happy user of Qooxdoo. :) > > Regards, > > -Bee- > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
