Hi, I plan on not using any qx classes other than Class/Interface, really. All other classes will be the classes that I wrote.
I'm not sure yet on how to package the entire thing. Having a standalone library not requiring the user of it to use qooxdoo himself seems compelling, though. For now I mainly focus on writing the library itself; I can think about how to package it later, too – my source/class folder won't go anywhere. ;) Thanks for your help so far, I'll check it out and try to switch to a qx.Desktop toolchain with a server-type application later on. -- View this message in context: http://qooxdoo.678.n2.nabble.com/How-to-use-Qooxdoo-Core-OOP-Standalone-tp7584309p7584319.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
