A SWZ is just a signed RSL. Unsigned RSLs are SWCs.

http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:Flex_3
_RSLs

Will give you some more info.

 

Gk.

Gregor Kiddie
Senior Developer
INPS

Tel:       01382 564343

Registered address: The Bread Factory, 1a Broughton Street, London SW8
3QJ

Registered Number: 1788577

Registered in the UK

Visit our Internet Web site at www.inps.co.uk
<blocked::http://www.inps.co.uk/> 

The information in this internet email is confidential and is intended
solely for the addressee. Access, copying or re-use of information in it
by anyone else is not authorised. Any views or opinions presented are
solely those of the author and do not necessarily represent those of
INPS or any of its affiliates. If you are not the intended recipient
please contact [EMAIL PROTECTED]

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Sefi Ninio
Sent: 02 October 2008 12:29
To: [email protected]
Subject: Re: [flexcoders] component reuse

 

Hmm... I thought that for SWC to be lazy loaded as RSLs, they need to be
SWZ (which only Adobe can create)...

On Thu, Oct 2, 2008 at 1:53 PM, Michael Schmalle
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote:

> Is it possible to lazy load a SWC?

No, SWC have to be compiled with the mxmlc compiler into the app.

 

RSLs can lazy load component libraries though.

 

Mike

 

On Thu, Oct 2, 2008 at 3:39 AM, Sefi Ninio <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:

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]
<mailto:[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.ht
ml> ) 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 <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

 

 





-- 
Teoti Graphix, LLC
http://www.teotigraphix.com <http://www.teotigraphix.com> 

Teoti Graphix Blog
http://www.blog.teotigraphix.com <http://www.blog.teotigraphix.com> 

You can find more by solving the problem then by 'asking the question'.

 

 

Reply via email to