Try a compositional approach. You might design a set of classes that reference movieclips and delegate events to the class; this would be contrary to extending movieclips. This way you can design movieclips specific to the site and design the code specific to the logic.
You could even abstract the technical logic from the UI completely and write communicators/controllers that respond to events fired from the ui (movieclips). M. 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
