On 06/16/10 10:16, thron7 wrote: > On 06/16/2010 01:11 AM, Burak Arslan wrote: > >> 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. >> > Python would be an interesting alternative, but as JBB already pointed > out that would make Python not only a platform prerequisite, but also a > language prerequisite. The Json format is sort of a "neutral" syntax, > and there are Json parsers for many concrete languages, should we ever > choose to implement the generator in something other than Python. > >
I see some of the oop concepts reinvented to support json syntax. This adds another chunk of code that needs to be maintained. Replacing the json with python will simplify the generator. And I frankly don't think anybody's rewriting the generator in another language anytime soon. Oh, and this may be interesting to watch: http://hg.cython.org/cython-devel/file/tip/Demos/freeze/README.txt On 06/16/10 10:30, Fritz Zaucker wrote: > I'd have to write > qx.Class.import("qx.ui.form.TextField"); > var tf = new qx.ui.form.TextField(); > > right? Assuming that qx.ui.form.TextField has all import statements for the > classes it uses already. And that would mean that there are many imports > duplicated all over the place, as each class would have to be > self-containted. > > I thought that's what computers are for, to automagically do the > obvious for me. > > I agree that it sounds like a step back, especially when one has to deal with circular dependencies. (classes that try to import each other) But we have some form of import statement with any other programming language i'm aware of anyway. So if it will mean to get rid of the ./generate.py source step, I say so be it. (oh and you most probably will do the imports before qx.Class.define() call) > I think Qooxdoo provides plenty of means for trying for free (e.g. > Playground, Demobrowser, and even a automatically generated standalone > application). > > For small snippets, yes. but these solutions are not appropriate for, say, a quick qooxdoo app with a few screens to see qooxdoo's potential to solve a real-world problem. I think this is important step for someone who is evaluating qooxdoo. ------------------------------------------------------------------------------ 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
