Hi everybody, Very interesting post indeed. I Think nearly everything has been covered so I only will make some comments and suggestions.
1) Indeed, Qooxdoo isn't so famous - I didn't say 'powerful' ;-). Every javascript newbie developer will use Jquery instead because they don't need the strong widget abstraction. They only will use scripts made by others (it's so easy for them because they only need to include the files in their html code and don't need to build an app) or work with the bom structure because they plan to generate html, not javascript that will generate/display html. Maybe a good approach - it's just an idea - would be to create a lot of bom contribs - like the overused lightboxes effects and so one... So even newbies/simple bom contrib users would try to use what make qooxdoo so powerful in the end. Personally, it's sometimes frustrating for me to be forced to use jquery for all theses common html/js things (lightboxes, fisheyes and accordion menus) in the traditional pages but I don't have so much time to spend on refactor this for qooxdoo. I know it's a bit like "reinvent the wheel" but I'm sure it could help making Qooxdoo more used by newbies. 2) The contrib repository is a bit like a mess. It would be so nice if there was some hierarchy or categories... 3) Maybe it would be nice if there was a config builder or a gui for the compiler. People may take a lot of time first to figure out how it's working. And sometimes, people are not aware of all this config declaration variables than can help in the build/source process (like copying, including files ...) And another great feature with the config builder would be to have some more config.json templates than the common ones. For instance, include the forms elements in a whole package directly ... ? 4) Indeed, the mandatory "rebuild process" is sometimes frustrating. Personally, I edit sometimes directly the build script file to do simple things like add a new resource file (and to be honest, sometimes I prefer directly use the full http path to the resources than using the alias way to do because I know that it won't force me to rebuild the whole qooxdoo app if I plan to add other images after the first build) Voilà, I hope it helps :) Best, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/speed-of-development-tp5168583p5181589.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
