Yes, this is a valid approach also, which i'm using quite often. But if we load the classes anyway, including them right into the final swf would make deploying a little bit easier.
My first idea regarding SWC was to be able to create SWC from Haxe code, this way we would be able to use Haxe "under the hood" right now in normal Flash projects. Also every now and then my customers get a swc component only, but not the complete sourcecode. So for me SWC makes perfect sense. If i just had some time ;) Cheers, Ralf. Jens Halm wrote: > Hey bokel, > > meine Mails werden von der Liste rejected. Anyway, jenes hätte mein > Beitrag werden sollen: ;) > > > >>My goal is to be able to use large precompiled binaries. >>For example, if i use a big library like AnimationPackage, i'm expecting >>to see some more improvement in speed. > > > With libraries I prefer to load (not include) precompiled SWFs and > link my application code to intrinsic classes of that library. > For large applications with multiple modules (SWFs) linking the same > library this approach seems better to me than to compile the library > into each individual SWF. > > > Carbonara! > > Jens > > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
