Hello, Hugh thanks that you mentioned qxtransformer.
In fact qxtransformer is quite stable despite on alpha label on our site. There are a lot of features which helps to build application GUI in XML. Includes and macros, XSD which brings autocompletion with documentation from API viewer to any IDE, creating own widgets, import existing widgets written in pure JavaScript (now you can use them in XML) and so on. Now qxtransformer works with 0.7 branch and we are going to integrate it with 0.8 because it is quite stable already. It will be next release for us. But qxtransformer is not intended to work at run time. In other words it processes xml at build process time. Maybe it can work at runtime as well but it's performance hit for your application. And because of it we chose build-time way. Any generation process is performance hit, especially if generated application/part is complicated. If anyone needs some more information can join our google group (see qxtransformer.org). Best regards, Siarhei Barysiuk On Tue, Sep 9, 2008 at 12:22 PM, Hugh Gibson <[EMAIL PROTECTED]> wrote: >> That is a software innovation. Basically, you go on our web >> application (that I hope to be able to do with qooXdoo) to define >> your need, the functional specification for a business >> application, you click on a button and you see the result (that I >> hope to be able to do with qooXdoo) >> It could be used from just validate spec with functional team, >> producing some kind of prototype to the tech team or just go >> directly to production. >> Our product is able to produce a full information system stack : >> the GUI, the business logic, the database schema, some test data. >> Thas is restricted to business application that manipulate >> persistent data with rules and workflow states but no scientific >> calculation, no drawing application like CAO or embeded industrial >> things or ... >> For now, we will take into account new application created from >> scratch and then we have plan for integrating existing application, >> existing data or use existing system. > > There are two approaches to this: > > 1. Create a new application with appropriate classes, dialogs, edit boxes, > backend databases etc. which appears to be the way you are going. > > 2. Create a meta application which reads the database schema, positions > and numbers of edit screens, menu specification from a large JSON object > or XML file and creates the UI and database on the fly. > > The advantage of the meta application is that you don't have to > re-compile it every time. Just write it, compile it once, and then > generate the appropriate JSON object or XML schema in your portal. Run > the application with the JSON/XML and you have the user's application. > > Also check out QX Transformer at http://www.qxtransformer.org/ though > it's early days yet for that. Perhaps some more work could be done on > that approach. > > Hugh > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
