> I'm progressing but still don't work. > Questions : > > It's about how or when "playing" the dependency. Say application A > needs application B. It implies that in the config.json of A we found > a libraries section pointing to B. > OK. Now if I generate build or generate source the application A, what > should happen ? Do I have to generate build and/or source of B before > myself ?
That is a good question, but I gave you the answer already, you just need to think about it. I wrote that your libraries, like B in your example, are treated just the same as the qooxdoo framework classes. Do you need to generate a build or source version in the SDK before using the classes in your app? - No. > Will it be done automagically by the generator ? There isn't really much magic involved. The classes of a library are referenced directly in the source version (like the app classes), and their compiled versions are put into the result script of the build version (like the app classes). That's about it. > In the build version of A, everything qooxdoo is included, is it also > the case of B ? You mean all necessary classes from the qooxdoo framework? - Yes. The same with the classes of B. Those that are needed are included. > So in case of build version of A, at runtime, I don't > need B to be there ? Nope. > In the source version, A doesn't contain B and so B has to be there at > runtime, is that correct ? Yep. > Also, witch build will the most find errors, missing references, raise > warning (?), reveal issues and potential issues ? I guess this is the > build because of all optimisation that need to be done. I'm not sure I get this question. The source version is generally better for development, since there are a couple of checks active that are disabled in the build version. At build time both versions will spot syntax errors, and will warn about unknown classes (if that is what you mean with "references"). You will get more warnings at run time in the source version, as I said. This is the usual mantra: "Develop in source, do build when you're fine". T. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
