Assets in a seperate SWF are loaded and included at runtime.
Assets in a seperate SWF are loaded and included at runtime. Assets in a SWC are loaded and included / compiled at compile time. You can also directly embed assets within the main app SWF at compile time (check out the Embed meta data).
Of course, you can also load individual assets (such as a PNG) directly at runtime. As far as which is better, it really depends on what you are trying to do, and how the assets are used. Mike.
Thanks! This really clarifies the difference for me. – defmeta Oct 8 '08 at 20:29.
SWC is what you use when you're looking for a library to compile into your app. You have access to the classes and can import individual parts. SWF is more likely what you're looking for when embedding graphics.
Here's the docs you might be interested in: livedocs.adobe.com/flex/3/html/help.html... I've been having good success with SVG for images, but there's some caveats since Flex only implements a subset of the features.
I have no real reason for doing this so it may be incorrect but I usually create SWF's for things that need to be loaded during runtime and SWC's for things that need to be available for design time.
A SWC is simply a SWF and some metadata wrapped into a zip file. Other than the fact that runtime loading of SWC isn't supported, I don't think there are any major differences between using the two formats.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.