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
