Hey Scott, I actually thought of creating a SWC as well, but I wanted to leverage lazy loading into the main app, that's why I thought more along the lines of a module loaded first time it's needed. Is it possible to lazy load a SWC?
On Thu, Oct 2, 2008 at 10:17 AM, Scott Melby <[EMAIL PROTECTED]> wrote: > I would be inclined to use the component compiler > (compc<http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_22.html>) > to build a component into a .swc library (think flexlib) that you could then > easily use from each version of your application (just load the .swc as a > library). > > hth > Scott > > -- > Scott Melby > Founder, Fast Lane Software LLC > http://www.fastlanesw.com > > > > sefi.ninio wrote: > > Hi everyone. > > I have a functionality that needs to be implemented both as a > standalone app (for users with restricted access) and as a module in > the main app (for users with full rights access). > > In the effort of code reuse (and laziness, of course), I'd like to > implement the functionality once and pack it as a standalone > application and as a module to be loaded inside the main app. > > I am in the middle of the process of thinking how to achieve this, and > would appreciate any suggestions the community here might have to offer. > > I thought of packing it as a module and make both main app and > restricted app load it as a module - that seems the obvious approach, > but I'm curious if there are more elegant ways to resolve this. > > Thanks, > Sefi > > > >
