Hi voger, when for example working in a Node.js environment - say writing a CLI tool or a web server - there will be no visual representation of your tool/program. So the widgets qooxdoo offers aren't helpful. But if you like our class system you can still use our OOP-style and the features it provides (mixins, interfaces, dynamic getters/setters ...).
That's the purpose of qx.Server - provide the subset of qooxdoo that in such an environment (i.e. DOM-less) still makes sense. The "Server" part in the name is just a hint at it's most probable use case. Does this help? If not, feel free to ask more concrete questions. Regards Richard ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
