On 08/08/2013 09:17 AM, Airblader wrote: > Not quite, no. I am writing a library myself, which is a collection of > classes built upon qooxdoo's OOP layer but does not contain an application > itself. So if I understand you correctly, I can still use qx.Desktop and > build a server-type application, right?
Yes, the SDK that is distributed as qx.Desktop (and qx.Mobile, for that matter) contains everything, also all bits and pieces for server-type applications (particularly the 'server' skeleton). You just have to be aware that there is then basically nothing to stop you from using framework classes outside the qx.Server scope. So don't start using qx.ui.* classes for your server developments ;-). > In the end, the "user" of the library will only use the class files I write > and decide on their own whether they use a node environment or not, for my > own development purposes I want to leverage the toolchain for testing etc. There is an interesting issue of packaging here. Do you plan to wrap up your own library classes together with qx-oo in a single .js file? Or make them an own .js file, requiring the user to install qx-oo separatly? You could also distribute it as a normal qooxdoo library, contribution-style [1]!? - Keep us updated how you proceed. T. [1] http://manual.qooxdoo.org/3.0.x/pages/development/library_custom.html ------------------------------------------------------------------------------ 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
