Skip navigation
Currently Being Moderated

Should I use a shared library?

Jul 20, 2010 2:27 AM

Hi,

This is the setup. I am working in two different applications, one to be compiled for desktop use (AIR) and one to be compiled for the web. They are part of the same project and use the same visual components, but they are completely different apps. When a visual component is changed in one application then it should also change in the other one.

 

Is this a good situation to use a shared library fla?

 

I am new to the concept of shared libraries and I am considering the options.

 

On one had I would not have to update 2 applications everytime I change something, on the other, I would always have to recompile the library folder when I do the smallest changes to a component.

 

Could you give me your opinion in this?

 

Regards,

Ana G. Pino

 
Replies
  • Currently Being Moderated
    Jul 20, 2010 10:27 AM   in reply to Ana G. Pino

    in your case, yes it would make sense.. I'm just not a big friend of RSL's.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2010 1:31 PM   in reply to Ana G. Pino

    The reason I don't like RSL's is just because we've created our own framework that handles all the assets sharing through multiple projects using XML & SWF files, our framework takes care of all the assigning and loading.. but since that is not an option for you I will not go into the detail, in your case I would really use RSL's.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points