It may be a good idea to split this into two projects. One would focus on developing an XML schema to describe a qooxdoo application and converters to generate the javascript code. The converters should support multiple languages (php, java) and possibly even XSL.
My main interest is on the php server side aspect to provide tools for developers to generate this XML definition easily and to provide a framework that can also hold business logic written in PHP. I would definetely participate in the definition of the XML schema and the converters (especially the PHP one) but I am not sure if I am the best person to head this project as I dont have the in-depth knowledge of qooxdoo where it is headed and how the XML schema should be structured to stay flexible. I am hoping that by using XML and converters to generate javascript that we can bi-pass the verbose qooxdoo api and directly define objects in their internal and private structures. I am hoping that this would speed up loading times. In addition we need a way to load sub-components of an application on demand and have the client add the definitions to an already loaded application (like flash does it with include files) so we dont have to load the entire app at once. Ideally there would be a way to un-load components as well and reload them so that they can be debugged without having to re-load the entire qooxdoo app and navigate to the same context again. So have two projects? "qooxdoo-xml" and "php-qooxdoo,java-qooxdoo" Christoph -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Alex Sent: Monday, April 03, 2006 3:19 PM To: [email protected] Subject: Re: [qooxdoo-devel] qooxdoo / PHP framework project Christoph Dorn wrote: > I am interested in leading a qooxdoo / PHP framework project. I am not > sure what the best way to go about this is. > Hi Christoph I have read the remainder of this thread, and as far as I can see the proposed framework is XML-based. Is this correct? What PHP-centric parts would there be? I think it would be valuable if there was a high-level architectural diagram showing the layering you had in mind for this project, such as where XML is generated, parsed, data exchanged, JavaScript written, and language-specific callbacks used. This would allow further discussion not only about the technical approach, but also which projects (Qooxdoo, PHP-Qooxdoo, Java-Qooxdoo etc) should develop which layers and modules within those layers. I'd ideally like to see server-side language usage minimised and kept as a very thin stub over the XML with perhaps communication over an agreed protocol (I'm a big fan of JSON-RPC as mentioned on this list in the past). If the community can agree on the best technical architecture and layering for Qooxdoo-specific server-side interoperability, I am happy to assist with a Java port of the server-side code. Cheers Ben ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
