We got to the point where the posts on the Principles of OOP and Design Patterns and the discussions of introducing Design Patterns to the workplace became so numerous that they were difficult to locate on the blog. This is the first index that we have, and as we continue to grow, we’ll have to add more. (We are certainly nearing that point with MVC and Pure MVC posts.) So, in the “Categories” section of our blog, we’ll be adding indices as needed. Look for the Index category to locate all indices.

Principles:

OOP and Design Patterns Ready for Work
• This post includes a quick guide to all of the principles discussed in the form of an AIR application that you can store on your desktop for a quick reference.

Link

Magic Table: What Varies in a Design Pattern

• Download Magic Table AIR Application

The Liskov Substitution Principle
Link

Program to an Interface; not an implementation
Link

Favor Object Composition over Inheritance
Link

Separate what varies from what stays the same and encapsulate what varies
Link

Objects should be loosely coupled
Link

Classes should be open for extension but closed for modification
Link

High-level and low-level modules should depend on abstractions (Dependency Inversion Principle)
Link

Only communicate with closely related object (Least Knowledge Principle)
Link

High-level components can call low-level components, but low level components never call high level components (Hollywood Principle)
Link

Your class should have one and only one responsibility (Single Responsibility Principle)
Link

Is Your ActionScript 3.0 Design Good? : The Three Keys of Good Design
Link

No New is Good New: Using Inheritance, Composition, Delegation and anything else other than New in ActionScript 3.0 Design Patterns
Link

Design Patterns at Work

Why Design Patterns?
Link

Strategy Design Pattern for Work
Link

Decorator Design Pattern for Work
Link

Not at the Children’s Table Anymore
Link

ActionScript 3.0 Developers: The Children’s Table Revisited
Link

No Time for OOP and Design Patterns
Link

Take a Design Pattern to Work Part I: Identifying the Problem
Link

Take a Design Pattern to Work Part II: A Little OOP
Link

Take a Design Pattern to Work Part III: Loosening Up
Link

Take a Design Pattern to Work Part IV: Establishing a Design Pattern Foundation
Link