Kenny, Thinking about it, I would be interested to know how you handle dependencies between qooxdoo classes in qooxlisp.
Do you generate the initial GUI from the Lisp code using the Generator, or do deploy your own dependency tracking and class packaging? Then, with the user interacting with the GUI, you said something like you would be sending JS strings from the server and eval them on the client. Do those strings introduce new dependencies, e.g. use so far unused qooxdoo classes, or do they just manipulate what's already there? If they introduce new dependencies, would those JS strings themselves contain the additonal class code? Or do they expect that all necessary qooxdoo classes be already at the client? Thanks, T. On 05/24/2010 09:53 PM, Kenneth Tilton wrote: > Screenshots: http://github.com/kennytilton/qooxlisp/downloads > > Intro: http://wiki.github.com/kennytilton/qooxlisp/ > > Congrats to the qooxdoo team for a great product. > > kt > ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
