Of course inheritance, polymorphism, encapsulation, etc. come much later,
and design patterns even later. No one would dispute that, I think.
I'd disagree a little. Encapsulation especially, is a really simple concept.
It's about organization and teaching students to stay organize - ie to keep
cats in one class and dogs in another is not advanced - no more so than
having them build a function that can be reused.
Lots of programmers never need design patterns as they don't help much
unless your architecting large apps, and lots of Flash programmers aren't
developing those kinds of apps. Keeping your code organized however should
be taught from day one and certain oop concepts are perfect for that.
It's pretty awesome to show students something like a utility class that
might store a url for a php script - and use that script in a bunch of
movies... then show them how one simple change in the class affects every
movie. This is the kind of thing they will appreciate and make use of.
Newbies figure out templates in Dreamweaver... sticking code in a class is
about the same.
I typically use a combination of OOP and procedural - keeping code pertinent
to a given movie in that movie if it makes sense, while using classes to
store code I use in multiple movies. I usually find it pretty awkward to try
and objectify an entire project - it just doesn't help. I find the combo
works quite well for me - and besides, it's still all oop if you think about
it...
Dave -
Head Developer
http://www.blurredistinction.com
Adobe Community Expert
http://www.adobe.com/communities/experts/
_______________________________________________
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
