Yes, thanks, it clarify the use. One more question, because a form should not evolve at runtime, why not saving the real qooxdoo form generated currently at runtime ? This would improve speed, so at runtime, the only thing the client side will see is a "normal" qooxdoo js file produced by the generator from the json string that describe a form. In other words, each client connected recompute the form each time.
On Sep 26, 2009, at 11:21 , MootCycle wrote: > > Right now, we're just copying and pasting (and doing some manual > editing) > from the designer into a text file which is stored on the server. > It's very > low tech. ;) At some point, we want to add a server component that > will talk > to the designer directly and save forms on our custom server. I > don't think > that server code fits into this contrib. > > With the contrib as it is today (revision 19263 at the time of this > writing) > the Blueprint framework does provide functionality for generating > forms > inside of any qx application if you include it into your project. > All you > have to do is add the library to your config.json file, write json to > describe your form, and use the blueprint.Manager class to generate > your > form. In the near future, I'm hoping to get the designer to a level of > functionality where you wouldn't have to write the json directly. > > I hope this clears things up. Let me know if you have any other > questions. > > -Dan > > > Jean-Baptiste BRIAUD -- Novlog wrote: >> >> So, on architectural point of view, I don't get the big picture... >> How are you using the designer yourself ? >> It produce json string describing a form, but what to do with that >> description ? >> >> ------------------------------------------------------------------------------ >> 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/New-qooxdoo-contrib%3A-Tartan-Blueprint-Serialization-and-WYSIWYG-Form-Designer-tp25622063p25623653.html > Sent from the qooxdoo-devel mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
