What are the pros/cons for using modules vs libraries in order to provide a dynamicaly loadable functionality (UI as well) to different applications.
probably. I know modules are compiled into SWF and libraries are compiled into SWC. But can libraries be loaded at runtime? Meaning that the application has no compile time dependencies on the library. At runtime some code determines that some functionality is needed and loads the url associated with the library (SWC or SWF, I don’t know), instantiates some classes and possibly attach those to the display list.
It’s not quite as automated as that, but yeah, you could do it.
You compile the common stuff into a SWC, then you can link to it.
Here is some more information on the subject: http://flexscript.wordpress.com/2008/11/15/using-runtime-shared-libraries-utilizing-flash-player-cache/
Since this is in Actionscript, do you mean the difference between SWC and SWF?
Really, the difference is next to nothing. The only difference is basically that a SWF can be displayed on the web and a SWC cannot. They can all do the same runtime sharing type stuff that anything else could do.
If that’s not what you meant, care to elaborate a bit more?