MODx could produce the data needed to drive OpenLazlo projects, just like it can produce the XML needed to drive flash UIs. It would not be a trivial process though.
MODx could produce the data needed to drive OpenLazlo projects, just like it can produce the XML needed to drive flash UIs. It would not be a trivial process though.Interesting! That’s the way I thought about it: Having a modx-backend (i.e. manager)for the house-keeping and content-management in the narrow sense plus some modules, for db-access for instance, but the output would be something "flashy" and web-app like, not just jumping from page to page...
From an open laszlo perspective, getting the documentation out of them to effectively replace their JSP data servers.You’re right! I just checked the docs and well: for a full fledged integration you would need to replace a lot of that JSP J2EE stuff to mimic a laszlo-server. For a 100% replacement you would have to mimic tomcat with PHP which is, I think, impossible.
1. Less is more. MODx admin interface should be more clean and organized. Moreover the project website should eliminate any hype or buzzword and focuse on documentation and support. An updated list of MODx powered web sites should be added. Don’t forget that the best promotion for a web app is made by its happy users on their blogs.
That would be a module, then. I don’t see it as being part of the core installation.