Thank you very much. Merci beaucoup! When you send them to me, we will put them on the blog so that everyone from Paris to Québec can get them.

Amicalement,
Bill

Yes, good idea, je vais faire ça !

Patrick

Why not translate the text files to French? We’d love to have it in French as well as English.

Bill

For the catalog I was just wondering if I didn’t understoud how to see the other.
With my knowledge of design patterns I could not help a lot on that project.

I didn’t interpreted well the meaning with the painting, though interface was the soldiers :)
I very apreciate your comparison between oop and reality.

Patrick

The Air Catalog is a project I started and invited others to help out if they wanted. So far no one has jumped in, and so I’ve just had time to get the first set of design patterns done. I’ll get going on the rest.

The Manet painting has a wall representing “encapsulation” and variation resides on the far side of the wall! (Who knew that Manet could be so helpful?)

Kindest regards,
Bill

Thank you to confirm my feeling ! Then maybe it have an influence on how widely the beginner uses inheritance.

I was really impressed by the image of the painting of E. Manet with the word “interface” above the soldiers, maybe they are the interface between those who gave the order and the sentenced ?

In your Air Catalog I can only see the creationnal patterns, are the other not already in the catalog ?

Amicalement aussi,
Patrick

I’ve wondered about the same thing myself. The inheritance in a language is organized with a different mission than design patterns in an application. However, you will find certain design patterns even in languages. (I believe there’s a Template Method tucked away somewhere in ActionScript 3.0.)

The structure is “fixed” and I’d certainly be nervous about a language that wasn’t. At the root of the classes is the Object class; however, you will find other Top Level elements as well.

Amicalement,
Bill

Now I think that I was wondering that because it looks a bit strange that the as3 native class seems to be made with a lot of inheritance.
When we see all this inheritance it’s a little bit hard to think that inheritance is not neccecary a good thing.

Maybe as3 native are like that because they are for a more definite use and not will change, they are tools for all the user of flash and in that it’s a “fixed” structure ?

Patrick

It’s always important to keep in mind what the principle attempts to do. (Also, keep in mind that those little ‘reminders’ are not literal translations!)

My own rule of thumb is to only subclass from an interface or abstract class–implement or extends. That’s also the Liskov Substitution Rule.

If you’re subclassing beyond an interface (including abstract classes) you’re making it tighter and more difficult to change. So, I would definitely not have subclasses from concrete child classes.

It’s funny you should bring up this query now, because the other day, I was taking apart a MovieClip of a truck I had made some time back. I created a separate class for each of the parts and I found that I could more easily control it and changing was quite easy as well. The composition was in taking instances of the different parts and reassembling everything. Then if I wanted to use any of the timeline commands, I’d simply use addFrameScript() and control it with AS3.

Take care,
Bill