Roger,
   Speaking of factories - I am missing something on object initialization when cloning instantiated classes - is it going to be possible in Flex 2 final? Something like this:
package {
 import mx.core.IFactory;
 import mx.utils.ObjectUtil;
 
 public class ObjectClassFactory implements mx.core.IFactory {
  public var obj:Object;
  public function ObjectClassFactory(cloneFrom:Object) {
   super();
   obj = cloneFrom;
  }
  public function newInstance() : *{
   return (mx.utils.ObjectUtil.copy(obj));
  }
  
 }
}
 
I do understand overhead - just want to capture "dynamically" built class and pass it through factory interfaces....
Thank you,
Anatole Tartakovsky
 
   
----- Original Message -----
Sent: Tuesday, February 21, 2006 12:46 PM
Subject: RE: [flexcoders] Your preference - Loader or createChild?


> createChild
>   Good: seems to execute more quickly than mx:Loader
>   Bad: one huge SWF
>
> mx:Loader
>   Good: multiple SWFs
>   Bad: seems to execute more slowly than createChild

Well, its certainly going to be a bit slower, since it needs to pull
stuff over the network and initialize it.

I'll be publishing examples at some point that demonstrates how to at
least make the things you load much more efficient.

I actually don't think mx:Loader is necessarily the best way to pull
them in.  I've built a new class that uses the underlying Flash Loader
class to load modules as a class factory.  This way you can choreograph
when they get pulled in a bit better.

Stay tuned.

-rg


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to