I have not had a chance to do much work on the PHP implementation yet, but will start on that soon. I have been working on a firefox plugin to get familiar with XUL. XUL and the mozilla/firefox implementation is very flaxible and powerful and I love the dynamic nature of it. All features and the ease of use comes down to a solid set of XML definitions to generate the code.
The PHP implementation should rely on a set of XML files to generate all functionality and code. These XML standards will be re-usable for any other server language implementation. I don't believe in extensive planning and conceptual work to define the definitions up-front but rather come up with a solid foundation and refine the definitions while building a prototype application to read and use them. One such definition type is a description of each QX Widget and its capabilities. Maybe we can auto-generate this from the documentation or define it separately and merge it into the documentation as it will contain important information that the decoumentation can benefit from. Information covered would be supported events, allowed parent and child widgets, supported properties and methods etc... The definition must have capabilities to inherit from superclasses to avoid duplication. If anyone has ideas about how we can obtain the widget definiton information or wants to get started on defining/generating these that would be great. Christoph -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Boulanger Sent: June 21, 2006 5:53 AM To: qooxdoo Development Subject: Re: [qooxdoo-devel] Experiences with webapp frameworks integration > 3. Dynamic UI generation > I have to admit that I haven't used the great-sounding qxBuilder yet. > Like I said, I load the entire UI in one page and that's it. > What's a typical use case, what's the performance like, and what are your > current benefits in a real project? [...] > There's only one other integration issue, and it has nothing to do with > qooxdoo:Templating engines for web apps are usually XML-based and can't be > used at their full potential (if at all) for JavaScript. > How are others approaching this? Hi Danny, there is a client-side qxbuilder, which parses xml-files with javascript and, though well-written, is quite slow (sometimes leading to a script timeout error on complex widgets in thunderbird, grinding to a halt in IE), and a fast PHP implementation, which builds on, and extends, the syntax of the JS QxBuilder. It works only with 0.5.x edition, not the namespace branch. Christoph Dorn is working on a more comprehensive solution, but I don't know how far he's gotten. I am quite happy with the QxBuilder XML syntax, it saves me from coding javascript for widget creation - i only need JS for adding additional behaviour. It's very good for reusing code. And since the XML validates itself, this saves me from typo's etc. I would love to have more people use QXML and get some kind of standard. However, it will be more difficult with the namespace branch because the direct relationship between class name and xml tag is lost. Cheers, Christian _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
