hi,
I suggest to group the "speed of development" thread into
what's-wrong-with threads. The discussion will be easier to follow;
especially for people who may want to help out with a particular aspect
of qooxdoo.
So, what's wrong with the generator? I have three points:
1) The .json configuration files: What are the reasons behind inventing
a domain-specific language based on json syntax? Why not just use python
itself? Getting rid of the .json syntax will help us get rid of a
considerable chunk of code and makes the entry fee cheaper.
2) There's no need for bootstrapping script to be generated for the
source version if the class import mechanism is made part of the language.
qx.Class.import("qx.ui.table.Table");
qx.Class.import("qx.ui.table.cellrenderer.Default");
etc.
Once you do this, qooxdoo becomes a pure js library for the source
version. It becomes basically free to try.
3) Why not (optionally) generate the parts automatically for the build
version? It'd make deployment a bit easier. (less docs to read)
e.g. ./generate.py build --with-parts
Please follow up with your ideas.
Best regards,
Burak
------------------------------------------------------------------------------
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
