I also do not think that the generator is the problem - on the contrary: the ability to generate highly optimzied builds is, as far as I can see, unrivaled in the framework landscape (think of source-hybrid or browser-targeted builds).
I agree with Thomas that the main challenge will be to adapt qooxdoo to the possibilities ECMAScript6 (factory->class system, also: databinding->proxies), as people will increasingly demand "native" solutions instead of framework inventions (no matter how ingenious). Also, qooxdoo will have to adapt to the ways people are used to work which will eventually converge around the NodeJs model. That is why I think that the contributions (the original subject of this thread) should be NPM modules, with some opt-out solution that let you integrate non-npm code. -- View this message in context: http://qooxdoo.678.n2.nabble.com/New-contrib-website-tp7585740p7585771.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
