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?
Ana G. Pino
Thanks for answering.
I have been trying to look for the best set up and I am not a fan of RSLs either. Do you have a recommendation of another way that I could set this up? Could you tell me your reasons for not liking RSL? And if you have worked with them any advice on how to approach them?
I know... too many questions, but I am really lost.
Thanks in advance.
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.
Since the sharing of resources would be offline I decided to have another fla where I have the library elements that are shared between more than one movie and then use an External Library. (Import ->Open External Library) and in the libraries of the movies that use those elements in properties-> source Always update before publishing.
Europe, Middle East and Africa