SWC statically linked and Embed assets are nearly the same, in both cases the assets are compiled inside the output SWF. *Cons:* * A con of this approach is the fact that size of your final SWF is increased with each asset added to the project and you have to recompile every time you change or add an asset. * More assets you use more time the user will have to wait in the load time. You can't partitionate your load times to make smaller loads on demand with shorter wait times.
*Pros:* * A pro could be that is easier to deploy since you only have to distribute your SWF, and you have only one load time and all the assets available after the loading is completed. * When the logic of your program use an asset you already know that is there, ready to be used. You don't have to check it or load it. *Runtime Loading:* *Pros*: * You can make bulk loading of assets on demand or grouping by need, the app will give the feeling of being more responsive, with smaller loadtimes in several places. *Cons*: * When you distribute your app you have to do it along with all the assets with the same relative path. * You need to be sure that where you are going to deploy your app you have permission to read your assets. * (I am not sure of this one) But I think that the assets loaded inside an app at runtime are not cached so they will take the same time the next time you load them unlike the embed assets. Cheers Martin Gonzalez www.web-adventure-kit.com 2009/6/27 <[email protected]> > I've seen various workflows recommending either one of the 3 ways of > getting Flash assets into a Flexbuilder Actionscript project. Can someone > summarize the pros and con of each approach? > ie > SWC > Embed > Runtimeloading > Thanks in advance! > > [f] www.flickr.com/photos/bitstream > [c] 416.668.0034 > [twitter] eco_bach > -------------------------------------------- > "...all improvisation is life in search of a style." > - Bruce Mau,'LifeStyle' > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org >
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
