I think we need to split this into two projects as I mentioned in one of my other messages.
Writing an application server (which this will be) is a tall order. Not in the sense that the coding is necessarily hard to do, but gaining community support and interest in it and growing its featureset in a standard and controlled manner. There are already a lot of frameworks out there that we can integrate with much faster than writing our own. It also gives us access to already existing communities. IMHO we should focus on a phased approach that will publish components as they become available so they can be used much faster than a complete framework. Something like this: 1) XML standard to describe a qooxdoo app 2) Implement the loading of the XML into a qooxdoo application 3) Define and implement an event callback system that can trigger server-side code based on UI events 4) Integrate the above components with several popular frameworks We can then do several things. We can standardize and abstract the XML to encompass other frameworks like dojo. Same for the callback system. We could also based on all common requirements develop a specification that a server-side framework should follow to fully support our UI XML standard. If no other framework steps up to the plate to implement the standrd fully we can write our own extensions for other frameworks or we can then decide to implement our own. The original proposal was to develop a standard as to how a complex qooxdoo application should be implemented. My main interest is in qooxdoo at the moment. Sure a general framework would be great and I am sure we will head in that direction long-term but I am looking for a solution now that I can implement into already existing applications. A phased approach will keep our options open and we can work on a framework if it is necessary but lets prioritize our milestones so that we can release viable components soon. I like the idea of calling it QxServer. Maybe "Qooxdoo Server Project". Emphasis should be on supporting and using as much existing technology as possible. Lets leverage what already exists. If this reaches general consensus I will draw up a diagram as to how I think it should be structured/architected from a high-level perspective. Christoph -- View this message in context: http://www.nabble.com/qooxdoo-PHP-framework-project-t1389226.html#a3748439 Sent from the qooxdoo-devel forum at Nabble.com. ------------------------------------------------------- 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
