Hi. > But what would be the standard, then?! What would be in the bootstrapper? ...
When talking about standard, I meant a standard way of packaging additions, not a standard set of packaged classes. A standard package format means most of the work is already done, but not quite all of it. There should be a possibility to generate parts without actually compiling them as part of the build process of the entire application, in order to have a real plugin mechanism, IMO. I'm thinking about something like maven for qooxdoo. You have lots of prepackaged components, with dependencies, and when you build your own library, you just add it to some repo - a public one on the net or a private one on your intranet. App developers then reference your libraries but don't actually include them in their packaged script. The bootstrapper, using the manifest, knows how to get the dependencies at runtime. Maybe you could even talk to the maven guys and use the public maven repositories. I can see two problems here, however. First, Javascript doesn't yet suport privates, so there might appear conflicts between libraries using globals - not that this is good OO practice, but bad things and bad code happen. Second, depending on browser settings, loading scripts from different sources inside the same application might suffer some restrictions due to security issues. br, flj ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
