Keep in mind the Principle of Least Knowledge–one of the principles that the Facade addresses–holds that objects should only communicate with those objects closely related. One of the giveaways that the principle is not being followed is “more than one dot” as you have in your example. The Facade helps the client communicate with less; not more. So in a system with a large subsystem (or a large number of interrelated systems) it makes sense to have multiple Facades to “keep the dots down.”

As long as you keep your eye on the purpose of design patterns and the principles in OOP on which they are founded, design patterns can be flexible.

Take care,
Bill

I understand the purpose is to simplify what the client must interact with (just the Facade) but say you were working on a very large project, and the Facade became.. lets say immense. While adding another Facade seems to be ruining the purpose of the ‘Facade,’ it could still simplify the project. eg. adding a Facade for each package?

com.gnoll.film
FilmFacade.as
com.gnoll.player
FilmPlayerFacade

What do you think?
Thanks,
Josh

Fowler’s GUI patterns look interesting indeed. However, given that they’re MVC-related, Chandima may do a better job on that. I’ve got the seemingly impossible task of trying to get the Prototype design pattern nailed down for ActionScript. Right now I’m working through the elements of recursion in the dp, and if you have any ideas about getting the Prototype right, I’d like to hear those as well!

Take care and thanks for the GUI patterns,
Bill

I really enjoyed your book and blog. I’m no pattern freak but your book & the Freemans’ are permanent residents of my desk.

When you have time, could you write some stuff on Fowler’s GUI patterns? (http://martinfowler.com/eaaDev/uiArchs.html)

Thanks!

It’s always our pleasure. I’m still hammering away on the Prototype and hope to get it done in the not too distant future.

Bill