Hey Pedro, i think with as3 the remark that OOP is only for big projects is not strictly true anymore (and it wasn't with as2 either). The thing is though that as3 forces your hand more than as2 did, it terms that every movieclip can be a class as well etc, so if you create one clip in the library that you want to add to the stage using as3, you're already OOP-ing. I think it would be better to say that employing complex design patterns and a rocksolid OOP architecture is more suited to big projects than to small projects. And with small I then mean small projects that are going to stay small.
The reason is mostly that employing a solid architecture and design patterns might require a lot of work up front, which will pay itself back as the project gets bigger and bigger. If your project stays small it's easier to manage your hacks and shortcuts. That isn't to say that you shouldnt design upfront or use design patterns in small projects, only that you must take care that the architecture and designpatterns don't become an end onto itself, they are a means to an end. For pluses and minuses, just a few I advise you to pick up as 3 design patterns, it's an easy read. Pluses: - common vocabulary makes communicating about your projects to other easier - time proven solutions prevent you from reinventing the wheel Minuses: - may make your application overly complex without good reasons to do so I saw an example once of a hello world application as a joke, which they refactored, ending up with a lot of classes and designs pattern, for just a hello world application. Like I said it was a joke, meant to teach you to match up the complexity of your application with the complexities of the design artifacts you apply. The best situation I think is where your framework allows you to start out very simple, and allows your application to evolve and be refactored along the way as demands on your application grow. We had that framework in as 2, and havent yet in as3 unfortunately, but I'm sure we will eventually:). regards JC On Thu, Mar 5, 2009 at 12:16 PM, Pedro Kostelec <pedrok...@gmail.com> wrote: > Hi > > Can you recommend a good source for learning OOP in as3? > Until now i found two books: > ActionScript 3.0 Design Patterns - Object Oriented Programming Techniques > By > William B. Sanders <http://www.oreillynet.com/pub/au/2820>, Chandima > Cumaranatunge <http://www.oreillynet.com/pub/au/2931> > and: > Object-Oriented ActionScript 3.0 by Todd > Yard< > http://www.amazon.com/exec/obidos/search-handle-url/ref=ntt_athr_dp_sr_1?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Todd%20Yard > >(Author), > Peter > Elst< > http://www.amazon.com/exec/obidos/search-handle-url/ref=ntt_athr_dp_sr_2?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Peter%20Elst > >(Author), > Sas > Jacobs< > http://www.amazon.com/exec/obidos/search-handle-url/ref=ntt_athr_dp_sr_3?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Sas%20Jacobs > >(Author) > Which > one is better? What i am looking for is a book (max 500 pages) with an > overview of the different design patterns, and some case studies or > examples > on how to write OOP > > I have one question that i can't really understand: Why people say OOP > programming is only for big projects? What are the pluses and minuses of > sticking to some design patterns? > > Pedro D. Kostelec > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
