Hi Franco, > more specifically, i need to have a separate file with only the *complete* > set of wx libraries/widgets, like the inline method, but without the > custom application embedded in it, as i will generate the custom > application code on the fly from the server part and i will inject it > at runtime.
That shouldn't be too hard. You can carve a custom set of qx classes into a js package. Similar to creating a low-level library [1], you could create a custom high-level library. You will have to make sure that all classes are included that your custom code might eventually want to instantiate, and, of course, you can exclude qx.io.remote if you so wish. [1] http://qooxdoo.org/documentation/1.1/setup_a_low-level_library > > This is needed as i'm working on a sort of "wxpython wrapper for make > desktop gui work without modification on the browser", where > all calls to wx from a standalone wxpython application written for the > desktop will run inside a special environment where all calls to > wxpython are intercepted and converted on the fly in qooxdoo code served > from a twisted nevow/athena live page daemon, used also for the > communication > between the gui part and the server side part. This is exciting, writing a qx rendering layer for wxpython. The RAP project [2] does this for SWT, and Tom Schindl has written a qooxdoo binding for Java [3], so there is plenty of stuff to learn from. It would be awesome to have a wxpython binding to qooxdoo. [2] http://eclipse.org/rap/ [3] http://tomsondev.bestsolution.at/2009/12/17/qxwt-1-0-0-0-released/ > > So, basically, how i can build an "inline application" where the custom > application code isn't embedded in the same file as qx things? Take a look at the above link to the low-level lib. You might also want to look at the Playground application [4] that embeds the qooxdoo classes comprehensively, and the "custom code" is entered in the edit area. Creating application code dynamically and sending it from the server has also been done in the community, but there are others more apt to report about that. HTH, T. [4] http://demo.qooxdoo.org/current/playground ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
