I did look at your prototype, and it is pretty clear to me that we're working along similar lines. I am hoping to contribute to the discussion both directly and through development of Blueprint. Since we're already using Blueprint in an internal product, I do have an interest in developing blueprint further along.
Personally, I think the biggest weaknesses for the blueprint format are in the idea of necessary top-level nodes like prerequisites, scripts, and functions. The idea of form level namespace ids is also somewhat limiting. All of these things exist in blueprint in its present form because I needed a way for a form to have scriptable behavior and also for form elements to be able to reference each other within a json file (no variables allowed). I'm not sure what you mean by the JSON being too technical. I've found that for our internal application, I've been able to design everything we've needed within the structure as you see it here. Could you explain a bit more about how you feel the format is limited? Thanks, -Dan Andreas Ecker-2 wrote: > > 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 > > -- View this message in context: http://www.nabble.com/Blueprint-JSON-Structure-Discussion-tp25722085p25798977.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) 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/devconference _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
