Hi. > Why - it's already possible! Are we talking the same thing? The 'bom' > skeleton and QxBuild are examples that have been mentioned. And I > explained the basics in a previous mail.
Still, QxBuild is not part of the official qooxdoo release, and the bom application is just an example that it's doable. Not every developer wants or can afford to develop a custom builder (I for one would love to, but am too time-constrained). Besides, there's the problem of standardization. A standardized way of packaging and deploying plugins/libraries of Javascript/qooxdoo classes on top of a basic qooxdoo-based bootstrapper would allow plugins/libraries of independent programmers to interact - a qooxdoo ecosystem could develop much faster than contribs which must be compiled into your source code would ever allow. IMO, it's very much like the relation between old monolythic, C++-based programs and programs for the JVM. Introspection, reflection and dynamic class loading make Java apps running on the JVM a much nicer network language. You don't have such features in monolything apps. Therefore I assume you don't want qooxdoo apps to be closed, monolything apps. Nevertheless, I can understand time and resource constraints. br, flj ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
