One way to describe design patterns is to separate the responsibility of classes in your application, therefore making decoupling possible. Eg MVC separates the model, view and controller, potentially promoting reusability, and the ability to work on either model, view or controller independently of one another.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roman Blöth Sent: Friday, 24 February 2006 3:06 AM To: Flashcoders mailing list Subject: Re: [Flashcoders] OT: Design patterns Anggie Bratadinata schrieb: > Stephane, that's a good article. [..] > Take a look at this interesting interview of Erich Gamma about Design > Patters (How to use): >>> http://blog.itpub.net/post/1087/48817 And - if not already mentioned here - think about buying the book "Head First - Design Patterns" by O'Reilly - definitely THE book for learning and fully understanding Design Patterns; there's nothing like this one out there (except maybe the other "Head First"-books). Get a free sample chapter (PDF) at ora.com. Best regards, Roman. -- ------------------------------------------------------------------- gosub communications gmbh | fredersdorfer str. 10 | 10243 berlin t [030] 29 36 39 1 - 43 | f [030] 29 66 88 84 | http://www.gosub.de ------------------------------------------------------------------- _______________________________________________ [email protected] 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 _______________________________________________ [email protected] 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
