Thanks for your response, but RSL won't fit in this situation. RSL are loaded at the application startup, however, I'm using module because I want to load the component by demand.
I've used modules before, but never been using modules that sits in a different project. It's important that the module will be separated from the main app/apps so that one developer can add features to the module, while another one can work on the loader app and have an up-to-date module compiled using source control. Cheers, Almog Kurtser. --- In flexcoders@yahoogroups.com, "Gaurav Jain" <[EMAIL PROTECTED]> wrote: > > The idea behind modules is to make your main app smaller (by breaking > into modules) so that you can speed up initial load time. And > load/unload modules when ever required. > > By default when you compile a module, flex builder optimizes it for > the main application - which means it does not add classes to the > module which are already in the main app. > > You can share the same module between different applications as long > as you don't optimize your module for any particular app. > > Module is runtime thing. Adding module into a library will not work. > > If you are looking to share common code across application and are not > interested in modules, you can use libraries. > > Also if you want to share code across different application but you > want to do so at runtime, you can benefit from using runtime shared > libraries. For more information about rsls see here > http://livedocs.adobe.com/labs/flex3/html/help.html?content=rsl_02.html > > Thanks, > Gaurav > > --- In flexcoders@yahoogroups.com, "mydarkspoon" <mydarkspoon@> wrote: > > > > Hello, > > I've developed a small flex module which I used inside flex project. > > Now I want to allow different applications to use that module, so I > > thought the best way to allow them using it is to distibute the module > > in a flex library project. > > > > However, when I put the library project in the source path of new flex > > project and mark it as a module, I get compile errors telling me that > > the *new project* (not the lib project) can't find the module > > resources (locales). > > > > I think the lib project should be the one responsible of having these > > locale resources, not the flex project that uses it. > > > > in the flex lib project I put this in the additional compiler arguments: > > -locale=en_US -allow-source-path-overlap=true -incremental=true > > and added the locales to the source path: > > locale/{locale} > > (just like I've done in a regular flex project) > > > > > > Any ideas of what I'm wrong ? > > (When running the module in a regular flex project, I get it to > > compile fine with the locales) > > > > Thanks in advance, > > > > Almog Kurtser. > > >
