Yeah, there are some known bugs in the designer at the moment. I'm trying to figure out how the UI can clearly display a form and it's actions. The simple "design view" isn't enough. I think that particular bug has to do with a context menu action removing the object that fired the context menu event. I'm not sure that context menus on the design object are the best way to interact with those objects. I suppose it is what people will expect to work, so maybe that's how I will move forward. I'm certainly open to input.
I see no reason why the designer couldn't generate javascript code. The only downside with that approach is that it might be a lot harder to import that code back into the designer. If you want to take a look at how the json is generated, take a look at the __getJsonForNode and __getJsonProperties functions in the designer.tree.Tree class. Since there seems to be a lot of interest in different export targets, I will probably try to facilitate that by moving the json generation into a separate object. Hopefully that will mean if someone wants to add a javascript exporter it would be easy to do. It would be neat to see a qxTransformer exporter too. :) I am certainly open to changes in the project. One of the reasons we posted it here is because we were hoping people would be interested in using it and maybe developing for it. I'm particularly interested in getting help with how the UI should work, as I don't know enough about rapid application development environments. If you want to have a discussion about where this project is going, please let me know. I'd be very interested in your feedback. Thanks, -Dan Petr Kobalíček wrote: > > Hi, > > I just played with blueprint, and must say that you are working on > really interesting project. There are few bugs, for example when I > deleted control I couldn't add another one (it freezes), but it looks > very interesting for all us to create forms:) Do you think that it > will be possible in future to generate javascript code from the form > description and possible integration with custom components? Maybe > there can be some Renderer interface that can be reimplemented for > different targets (JSON can be just one possibility). > > I seen that you provide only our controls (blueprint namespace), will > be possible to include also pure qooxdoo controls? Currently it seems > that you have implemented some marshall/serialize stuff in your > components that looks like solution to your form demands:) > > I'm just asking, if this project will be really open to changes, I may > spend some time in future on it. I really wanted some UI designer and > your project is very close to my demands - click, click, drag, drop, > click, click, done:) > > Cheers > - Petr > > ------------------------------------------------------------------------------ > 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-tp25622063p25653947.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
