The non-optimized state of the code can be accepted, in my opinion, because the UI generation is done only once, at application setup, so the gains from any potential code-intensive optimization will be minimal.What is important for me, when coding, is to be able to quickly throw in a table with cut& paste without having to look up the quite complex syntax that is necessary to set it up in javascript. For example, adding or deleting columns is a snap in the declarative way, whereas in javascript, columns have to be numbered explicitly and their properties are dispersed over different models (the table model, the table column (resize) model).
Exactly my point, sorted top/down according to pain I would say - procedural - declarative - visualand on top of that, visual/dynamic such that you not even have to hit refresh for changes to be reflected.
Hmm, I have the dynamic side completely solved, being able to inject widgets into live pages at server or clients will (see http://nqx.thieprojects.ch , the calculator(s) are by no means present when loading the page, they are injected on the fly), seems I only need the transformation from declarative to code on the fly...
We then only need a visual tool >> declarative >> procedural, probably a cool website, which would let you do manipulations on every level, whatever is preferred at that time.
Werner
<<attachment: werner.vcf>>
------------------------------------------------------------------------------ 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
