> what still needs to be debugged are <qx:script> sections, > this might be a > problem when compressing the code. That's exactelly what i mean, the GUI is IMHO no problem but a "normal" app has not only gui, it has some kind of functions! And how to debug them inside XML (how to set a breakpoint for example - in pure JavaScript this is no problem but INSIDE XML???)
> > My test case to compare QxBuilder and a server-side solution is a huge > widget with 5 tabs, 10 Textareas and 30 -40 textfields. With > QxBuilder, it > takes 10 or more seconds to build the widget and I get a > script timeout > warning unless I insert some setTimeouts. I hope that pure > javascript will > be a bit faster - but to be honest, I don't know. I have so far simply > assumed that this would be the case. I think, javascript is even faster (many times faster) than parsing XML So i think, it is better to make a "offline" compiler -> just write the (error-free) XML and generate a javascript-script. The GUI is then ready (and error free and easier to make than writing code by your own) and than you can beginn to fill the functionality (and if this is ok copy it back to the XML - if you like) so that you can do the generation more than once) Olli ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
