I don't know about the Yard book, but the AS 3 DP book might be your
second book after something like Learning AS 3.0 at Oreilly. Unless
you feel ready to wade into it.
I don't think many people say OOP is not for small projects, but OOP
and Design Patterns are not the same thing. Any project can benefit
from OOP techniques, though I sometimes think that small project/
beginner programmers might be better off with a library of really
good static reusable functions. A full implementation of a design
pattern might be overkill for a small project since adds overhead and
might takes extra time to write code when sometimes you are trying
to do something quite simple.
An advantage of design patters on big projects is it usually makes
things easier to change, helps integration into bigger structures and
with other developers, provides standardized structure, etc..
On a small project, this might be less important but its still good
to have some sort of concrete pattern to stick to so your code isn't
a mess. A simplified MVC with a combined V & C might be something to
try or any other pattern that gets your data separated from your
logic to begin with.
Beyond patterns, OOP, etc., I think its really important to identify
those areas of your program that have the possibility of changing
over time and then focus your architecture, structuring, etc. on
those areas. For example, if you are doing a one off simple game,
then you might just right a main loop and leave it at that. However,
if you are doing a web application were the client wants to
constantly be adding "pages", then it might be good to consider an
MVC where its easy to change views.
On Mar 5, 2009, at 6:16 AM, Pedro Kostelec 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
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
David Benman
Interactive Developer
[email protected]
http://www.dbenman.com
(508) 954-1202 (cell)
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
