It’s set up for Flash CS4 and/or Flex Builder. All you have to do is to create a new CS3 Fla, and in the Document Class window in the Properties panel type in ‘Client’ (w/o the quotes) and that should do the trick.

If it doesn’t, let me know.

Kindest regards,
Bill

In the downloadable source files, Client.fla seems to having some problem because I couldnt open it in Flash CS3.
Can you please make the correct client.fla available for download.

Thanks in Advance .

Regards,
Sangram

What a great way to put it!

…anticipate unforeseen requirement changes…

In some way, most (if not all) design patterns help to deal with unanticipated requirement changes. And of course in the real world of Internet based programs, change is the only constant.

Kindest regards,
Bill

I’d like to translate this series into my language when I have time.

Personal story of mine, I used to work with “unstable” specs ( who doesn’t ? lol ) and patterns have been very helpful to anticipate unforeseen requirement changes, at least they can help minimize the impact. Strategy, FrontController and ModelLocator are those that I use most. And I’m glad that I bought your book ;-)

A certain irony lies in the fact that the first sentence of the GoF book notes that design patterns are difficult. Getting them into the workplace is even more difficult, but that part isn’t discussed as much. (Note to self: Suggest to Gang of Four to explain how to accomplish the latter.)

If anyone reading this blog can share a story of how design patterns came into a functioning part of their company, such comments would be most welcomed!

Best wishes,
Bill

Basically, creating a private variable or function is a good way to encapsulate the variable or function (method.) It’s just a good (and easy) habit for OOP. In the example, all of the child classes had to use the methods in the parent class, and by creating a protected method, the methods were encapsulated to the class and its descendants.

I believe a good OOP habit is to use private or protected access where possible to help sustain encapsulation. TK’s comments were helpful as well.

Kindest regards,
Bill

For example:
public class Whatever {

public Whatever() {}

protected function getValue():Object {…}
}

Only a class subclassing Whatever would be able to call the “getValue” method.

Access modifiers vary on your language. In Java, protected is similar but also allows package-level access. In AS3, no package-level access is allowed, it must be a parent-child relationship.

– TK

Cheers,

RyanL