Hi Christian, thanks for the info.
> did you see http://www.aptana.com/jaxer ? > > I think Aptana could be THE IDE for qooxdoo development if full qooxdoo > code assist and a qooxdoo extension for the Jaxer backend could be > developed. This would be so cool - a ready-to-go client-server > architecture for qooxdoo apps. I would guess that the Jaxer Server does > require much less resources than, for example, a Tomcat or similar > complex backend (not to speak of installation hassles), and one could > use one language (javascript) for development instead of several... (I > am writing this after spending hundreds of hours on assembling a PHP > backend framework to work with qooxdoo). Jaxer might look like a shiny new way of creating Ajax applications using JavaScript in a transparent way both on the client and on the server. IMHO however, it has fundamental disadvantages as it builds on the same ideas as "legacy" web frameworks. It is still based on HTML content being created on the server (this time allowing for "browser-like" DOM manipulations, not only templating, transformations, etc. as in other typical server-side web frameworks). This HTML content is then delivered to the browser and needs to get parsed (a second time, now on the client) to have some client-side DOM library play some tricks. This is far from the paradigm of Ajax applications that allow for highly-interactive user interfaces by dynamically manipulating only the client-side DOM and communicating with the backend in a very distinct, data-based way. I think Jaxer is mostly suited for smaller applications that involve just one, maybe a few developers, or for rapid prototyping. For any larger application with many users and/or scalable (often existing) backend infrastructure, I doubt that Jaxer is an alternative. I'd prefer a clean separation of responsibilities over the JavaScript-based transparency of Jaxer: * The single-language concept of qooxdoo for the client-side (JavaScript only, no HTML, CSS, DOM knowledge needed) * any mature and scalable backend in another language (Java, PHP, C#, etc.), typically implemented by developers with backend-specific skills * a robust and stable communication layer between those two (e.g. data models, qooxdoo RPC) I doubt qooxdoo with its GUI toolkit fits into the concept of Jaxer. Aptana may nicely try to combine client-side and server-side JS within the IDE, but still you have JS code on client and server to manage. Of course, a server-side (rather "DOM-free") JavaScript might see some renaissance (remember Netscape LiveScript?) in the future, but IMHO that is not a real thread to well-established backend technologies. Well, just my 2 cents, YMMV, ;-) Andreas ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
