Hi Dan, thanks for your comprehensive input and asking for suggestions. I'd like to remind you to take a closer look at the existing bug report and demo (if you haven't yet), that show some premature ideas of a declarative qooxdoo UI:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=2685 http://demo.qooxdoo.org/devel/demobrowser/index.html#test~UIDeclaration.html My first impression of your initial JSON dialect is that it is way to technical. But besides the naming of keys, you're absolutely right that we should strive for a JSON dialect/hierarchy that is most easily fed into the existing qooxdoo GUI toolkit, i.e. without much pre-processing. I doubt there'll be many alternatives at the end (besides the typical naming discussions), because it presumably needs to be a format that is most "natural" to qooxdoo's GUI handling. When focusing on the main idea of Blueprint first (i.e. form generation), Martin would surely be a great source of inspiration, but unfortunately he's on vacation now. Anyway, I'm sure there'll be many people interested in a broader discussion and proposals (Sebastian, Siarhei, etc.) ... TTYL, Andreas ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
