Ok, that makes sense. What is the benefit of going the classfactory way instead of extending a class and setting all the properties in a class constructor?
--- In [email protected], "Jonathon Stierman" <[EMAIL PROTECTED]> wrote: > > From the Livedocs: > > > > http://livedocs.adobe.com/flex/2/langref/mx/core/ClassFactory.html > > > > It lets your application automatically create instances (with properties > configured too!) without much input needed from you. Essentially, you > configure the factory with your class, and then set up some properties > to apply to every instance of that class. When you call the > myClassFactory.newInstance() method, the Factory automatically creates > an instance of the object, and injects the properties you set up into > the new object. > > > > So if you're ever creating lots of objects of the same type and details > over and over again... think ClassFactory. ItemRenderers are Adobe's > big example of this. > > > > Jonathon > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of valdhor > Sent: Friday, May 30, 2008 8:46 AM > To: [email protected] > Subject: [flexcoders] What is a classfactory and why would I use one? > > > > This may be a dumb question but I can't seem to find this in any > documentation. > > What is a classfactory and why would I want to use one? What can I do > with a classfactory? > > Any links to documentation/tutorials? >
