Hi > Pretty simple: the app developer has to throw a mention of any > "built-in" qooxdoo class they want to use into Application.js. By the > same token, any new class they want to use should be authored the > usual way, by adding a .js file and doing the generate step. That's exactly how I do it with the qooxdoo/nevow integration, although I do quite some JS programming for the GUI but I rely on the divmod/nevow JS enhancements, using qooxdoo objects only for the visualization of whatever happens in the live widgets. The nqx.thieprojects.ch site is up again, showing as an example a 'live' calculator with all the calculator logic sitting on the server. Silly to think that somebody would do that, but just to prove the point...
Werner > That might sound like it would lead to a lot of JS authoring, but one snip... ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
