Hi Christian,
This looks very interesting. Its great to see someone elses take on a general framework. I have been working on a general framework for PHP for the last few years and will be releaseing some components under the LGPL soon. My main focus was re-usable low-level components that any application can benefit from. One major requirement was that you can use these components within any other framework without conflict. I am hoping that the components will start to establish some standards for PHP like there is for Java so we can start interchanging components between different php projects/frameworks with a standard interface and no conflicts. Horde is good but has a too high level focus. Its easy to build a standard app but does not have a good architecture and no utility libraries to help you with more low level stuff. I think the goal for us should be to develop libraries that can drive a qooxdoo interface (create qooxdoo javascript with php and load data into qooxdoo) and can call application logic triggered by qooxdoo events. The libraries should be self-contained so anyone can incorporate them into any project like horde or mambo. This way we can have many people use them. The libraries should be structured in a way where they will also easily fit into a more comprehensive toolset (second phase) to facilitate all standard taskes when building comprehensive pure qooxdoo applications like you listed below (I think initially people will use qooxdoo to enhance their apps and may not necessarily make it their core platform. To enable this it will be important to only include required qooxdoo components into a javascript file so it loads faster and enables developer to offer a more powerful tool for a feature if the user's browser supports it). Its hard for people to change frameworks if they already like one that does what they need. Lets give them the tools and libraries to drive qooxdoo from their preferred framework? The framework I have been developing is very comprehensive and runs several commercial websites. I think it would be a perfect fit to also drive qooxdoo from PHP. Short from just dumping the framework code on the net (and not having the documentation and time to support) I have been thinking about how to best release it so it will be valuable and gain traction fast. The key is small components that already fit and work with many other frameworks which over time will grow into a comprehensive toolset which can be used by itself which would then represent the entire framework. Make different people responsible for different components so we can keep up with documentation, examples and support. What do you think? Whats your background and main experience with PHP? Do you use it in your job? Christoph -- View this message in context: http://www.nabble.com/Increase-exposure-awareness-with-visible-project-t1360587.html#a3715669 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
