Hi, I am almost through with updating my PHP backend framework "qcl" to PHP5 and the consistent use of the PDO database abstraction layer. In this process, I have made some updates to the RpcPhp and RpcConsole contributions. I am creating an infrastructure for fully automatic testing of RPC services. You can see a sneak preview here:
http://cboulanger.users.sourceforge.net/qooxdoo-contrib/RpcConsole/trunk/?serverUrl=../../RpcPhp/trunk/services/index.php&runTest=runAutomatedTests Screenshot is here: http://n2.nabble.com/file/n4880037/Bild_2.png As you can see, I am using the web service infrastructure of sourceforce to showcase the demo. This makes me wonder why we aren't using this more for the qooxdoo-contrib demos. I want to point out again that I think that the contribs need more exposure and in particular they need live demos with access to backend support. Sourceforge seems ideal: they provide server-side logic such as script languages, database, etc. Demo code could be automatically be uploaded with rsync and kept up-to-date directly from svn. But it would be best if this was not done individually by the contributors, but if there was a system in place that used the common webspace of qooxdoo-contrib and draw its code from the SVN. Cheers, Christian -- View this message in context: http://n2.nabble.com/RpcConsole-update-and-suggestion-to-use-sourceforge-webspace-for-qooxdoo-contrib-demos-tp4880037p4880037.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
