Hi Just a few remarks:
How do we get an even better qooxdoo framework?It's free and open, it has a decent licensing scheme and therefore the only way to improve it IS by contributing, on the list, with code, with helping out others, by advertising it and NOT by kicking the core developers to be more productive. They are for sure the ones who are the most aware what's missing and how to achieve it.
What if I'm an old dog coming from the desktop app scenery?Stop whining, it's never too late to learn and after all - it's your decision with whom you're hanging out - so please decide and stick with it, for the better or worse.
What if I need a super duper control which gives milk, wool and honey and clearly does not exist in qooxdoo? No problem, work can always be traded for money. I bet there are people on this list who have the time, the capabilities and the will to write whatever you desire. And all the better, if you decide that such a control could be made a 'same license as qooxdoo' contribution.
<rant>Just to reiterate it: We are after all talking about 'Free and Open Source Software' where 'Free' means 'free as in freedom' not 'free as in free beer'.
And as we are seeing more and more these days that our societies are built on lies upon lies not even your free beer will be free in the end!
</rant> So kudos to the qooxdoo developers and to all the contributors! Werner On 12.06.2010 04:56, Bee Jay wrote:
On 12 Jun 2010, at 07:02, Petr Kobalíček wrote: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.I'm quite satisfied with modern theme, I choose function over look. But I think the available widget is still very limited both on number and feature. :(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.+10! :D5. Better performance - qooxdoo is really slow compared to other toolkits.Overall, I think it's quite acceptable. But on some widgets (table?) and process (drag-n-drop?), the slow performance is noticeable. -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
<<attachment: werner.vcf>>
------------------------------------------------------------------------------ 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
