Ben Alex schrieb:
ChristophDorn wrote:
I really like the idea of using the XUL standard for qooxdoo application
layout. It makes total sense. From what I have gathered so far it
looks like
a good fit.
Hm. As much as I like XUL and the idea of qooxdoo being
"close-to-a-XUL-engine", I wonder if that is not way to much overhead.
Why not simply use the class structure of qooxdoo and mirror it in the
xml structure? Otherwise, the javascript modifiying the created widgets
has different logic than the pseudo - XUL code describing them. It seems
to make more sense to me to have, for example, a QxAtom with its
properties being a <qx:atom> node with the properties as attributes.
I was thinking of sometthing like
<?xml ...>
<qx:application
[Initializers here such as image path etc. etc] >
<qx:window
location="100,100" dimension="500,300">
[...]
<qx:eventListener type="close">
alert ("Window closed!");
</qx:eventListener>
</qx:window>
</qx:application>
Very close to the QxBuilder syntax. Added value could be:
- overlays (like in xul, to modularize the application>
- i18n (again, like xul)
But maybe you can explain to me the advantages of further abstraction.
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
