I generally prefer loading external SWFs for this sort of thing.  That way
the individual form SWFs are not dependent on the master SWF.  And you avoid
library bloat.  You could create a template that is a starting point for
building individual forms.

-Adam

On 6/30/06, Ricardo Sánchez <[EMAIL PROTECTED]> wrote:

I've just started to work in a big internet communication agency. We have
to
make 2 or 3 microsites every week. Each of which uses a very similar form
to
get user data.

All that changes from one to another is a couple of fields and the look of
it.

My question is: What's the best way to implement a re-usable class for
this
kind of work? Should I make a movieclip with all the fields and a class
binded to it and modify the clip everytime I re-use it? Or should I make a
class that loads different clips from the library?

Do I explain myself?

Thanks.
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Reply via email to