> 4 : use qxbuild : you will just have to include a big js file and you > are at very few minutes from your previous js tested in the > playground. You can enjoy qooxdoo power but ok, files are big. At that > time, it is not important, its not deployed on production, isn't it ? > > 5. after few days, weeks or months, *once you are convinced*, once you > have time, once the choice is done, you want more power and mor > eoptimization and, good news ! it is possible ! Use the Python tool > chain. Invest few days (maybe hours for good people) but now you are > ready to do that. > > > In fact, including qxbuild as an official qooxdoo possibility will not > prevent people who would like to drop the step 4 and go directly to > step 5 with tool chain. >
I have quite some sympathy for this rational, and in fact, in version 0.7 qooxdoo had this "big file" component, called "quickstart". But to support such an option seriously, some work would have to be done on qooxdoo (Petr probably knows best what I'm hinting at). What is hard to judge from our side is, how many people are deterred by the "obscure" tool chain, and how many by the sheer size of the "big file". I think we lose people on either end, the question is just which is more severe. Of course, as you say, all is fine for those prospects that take their time to read and make an informed decision, but, alas, how many proceed this way?! T. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
