1) ZoomNav X

2) Inheritence 
   - procedural button pattern
   
   FadeNav
- how could we convert this to be a scale nav?
- 1) we can add a crapload of if statements and a new set of arguments
- 2) we can duplicate the code and give it a new class name
- 3) Hard, but we can use inheritence
     - extends MovieClip, Sprite, EventDispatcher
     - standard STUPID inheritence example
     - how we can use it with template method pattern
     
   - remove duplicate code
   - write less code
   - create extendable architechute
   - class diagrams
   - UML
   - single responsibility principal
   - ask don't tell
   - strive for loose coupling, not always possible - don't force it
   - don't force oop rules, use them where they make sense
   
3) XML
   - represent any data
   
4) Min Gallery

5) Document Class

Homework try to make your gallery better
look over the gallery from las3
Write at least two subclasses for the Nav class
Link your navigation to something...?


