Ulrich Schreiner schrieb:
but back to my first question, i thought you want qooxdoo applications
to start quicker. hm, i don't see how a xml->qooxdoo converter which
runs on the serverside can help.
ok, you can try to load only those qooxdoo parts which are needed.
but: you have to "understand" the qooxdoo class hierarchy. well imho,
the easies and efficient way is to load "qooxdoo.js" (in its
compressed form).
sorry, but i really don't see the advantage of a serverside component
which parses XML and produces (qooxdoo specific) JS.
The advantage is that it looks nicer ... ;-)
No, but seriously, there is a huge advantage for using XML:
- you can avoid verbose, semantically redundant, and error-prone
javascript coding ("Verbose" seems to be my favorite word lately ;-) )
- you can deliver on-the-fly compressed javascript to the client of your
own code (not only of the qooxdoo core files)
- you can easily exchange GUI templates
- you could even, if you want, create converters from other GUI XML
description languages (such as XUL or Qt) or at least, rewrite those
with less hassle
- you can structure the XML to contain meta-information on the GUI
- you can use the same XML code even if the API changes - all you need
to update is the parser
As to speed: Server-side parsing is fast ennough to be not noticeable,
especially compared to the performance of QxBuilder. It has been one
idea of Sebastian early on, by the way!
Christian
-------------------------------------------------------
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
