Hi I don't have any experience with qxIDE or other declarative tools (there used to be QxTransformer but that seems to have disappeared - actually, I can't find qxIDE either!), but they did't seem to ever really take off. While it might seem a little hard going at first to write GUI in Javascript you can quickly speed up and it is very flexible.
If you're getting lots of errors compiling qxIDE then it's probably quite old and as you say, unmaintained - upgrading it is probably not a fair evaluation technique for getting to know Qooxdoo, given that you're going to hit problems that have nothing to do with Qooxdoo itself and while it will be a good learning experience those problems will also distract you from your evaluation. John On 17/06/2013 16:17, "mingodad" <[email protected]> wrote: >Hello ! > >I'm evaluating qooxdoo for use it on a project and I like the overall >functionality ready to use. > >After reading briefly the first chapters of the manual I've tried to make >a >small test a coding a container with a label and two buttons with a custom >look and feel, I endup with around 30 lines of code and found it a bit >verbose, I would prefer a declarative way of doing it like the ones that >tried to it with xml for example. > >But better than that I would prefer some kind of wysiwyg builder like the >qxIDE, so I decided to try to make qxIDE to work with qooxdoo 2.1.1, after >some intents I could reduce the errors a bit but I'm not sure if the >generated bootstrap code was hand edited in the original qxIDE because it >give errors that seems to be related to inclusion order of the >dependencies. > >Overal I did not got a good experience about the possible problems that >can >arise form the automated generated code and that makes me delay the >consideration of using qooxdoo. > >Some tools like the playground are very useful but having something like >qxIDE would facilitate a lot for newcomers. > >Why qxIDE was not adopted by the qooxdoo team (it seems abandoned) and >make >it part of the official distribution ? With a tool like that qooxdoo would >get a bigger audience and probably that would benefit the future of it. > >Look at this page for an overall evaluation of available frameworks >http://javascriptures.wordpress.com/2012/05/17/great-javascript-ui-framewo >rks/ >. > >Cheers ! > > > >-- >View this message in context: >http://qooxdoo.678.n2.nabble.com/Evaluating-qooxdoo-for-a-project-tp758388 >9.html >Sent from the qooxdoo mailing list archive at Nabble.com. > >-------------------------------------------------------------------------- >---- >This SF.net email is sponsored by Windows: > >Build for Windows Store. > >http://p.sf.net/sfu/windows-dev2dev >_______________________________________________ >qooxdoo-devel mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
