1. Our themes are built using compc, and specifying the framework swcs in the external-library-path arguments. This ensures that the framework classes are not included in the theme. For details on our exact method, look at the build.xml files in framework/projects/wireframe or framework/projects/halo.
2. The spark theme is being built into the spark framework. Yes, this does add a bit of overhead with the initial load of the RSL, but once it is downloaded it can be shared across all apps.
3. When compiling a theme, you must explicitly include your classes, and also do an include-file for your css file. Compc doesn't compile your css file, it simply includes it in your theme swc (with the include-file option). When using your theme with mxmlc, the css file from your theme is compiled and that is when the associated classes/skins are linked in. If you use external-library-path for the framework swcs, it will use the framework classes from the main app, which can either be statically linked or loaded from an rsl.
Thank you Glenn, that was helpful. Along those same lines, do you have a solution to this problem?
There are a bunch of icons and resource bundles being included in the library swc and I would like to know how to remove the icons and share the resource bundles between all the libraries using them.
And one last thing, when you have something like this in the frameworks/projects/spark/build.xml:
Is that automatically done when I create a library project? I'm looking through the window for editing library paths in Flex Builder, and it's including tons of framework swcs. Are these "external-library-path" items, or are they different? I've attached an image of the screen.
flex_compiler_screen.png 77.0 K