Just to throw in my experience to the mix, when I started out learning how to use qooxdoo I was quite enthusiastic and pushed ahead but the simplest of things seemed to be quite a complex task to complete and because the help / support pages were not answering my questions I turned to the dev mailing list for help.
However now I'm finding that I just can't be bothered to keep having to ask questions and my optimism and enthusiasm has waned somewhat. Please keep in mind that some users like myself, although technically proficient (I know C++, C#, Obj-C, PHP, Java, etc), do not have the time to learn all the ins and outs of a package like qooxdoo and need to just "get it done". I feel that qooxdoo removes a lot of the rapid application development that is usually possible with JS libraries. >From a constructive point of view, I believe that having example code on all the pages of the manual would help significantly. Perhaps this already exists and I just missed it? If it doesn't, maybe an "add code" option for developers who want to help out would be good? Drive-by learning using example pages is the life-blood of a library like this IMHO. As it stands, I have given up with qooxdoo because I couldn't rapid develop as fast as I would have liked. In an ideal world there will be many developers who have the time and patience to learn so much before jumping into a project but make no mistake, there are MANY like me who are also running so many other parts of the IT in their company that they just don't have time to read all the docs, all the API pages etc to get something working. In my case, I had two days to build an app that would do what we needed for some internal data management. In the end I just installed SQLYog on the PC of the user who needed to manage the data because writing an app with qooxdoo was too long winded. To reiterate the voices of others here, qooxdoo is great and I'm not trying to put a dampener on your development push; but every JS library I've ever used that's been a success for me is because of the very easy-to-Google examples all over the place. Rob Evans CTO mtn-i LTD -----Original Message----- From: panyasan [mailto:[email protected]] Sent: 14 June 2010 16:14 To: [email protected] Subject: Re: [qooxdoo-devel] speed of development Well spoken, J-P. I agree with all your points. Concorning the download-not-compile question, I think the plan is to provide a webservice where you can download a custom-compiled package -- this will combine the advantage of the compiler with the instant availability of a download. This should be a priority --- Ahh ---which means my own petty priorities will move to the back, oh, no ;- ) C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/speed-of-development-tp5168583p5177865.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 ------------------------------------------------------------------------------ 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
