You Might Also Like...

• 

  New Aid Game: The Machine Moves!

  126 readerswanted to move on from the original Aid Game, at least as far as the movement was concerned; so I fully fixed it up. With the new set of rules from the previous post of repairing the movement, I realized that if I didn’t generate fully operating movement states, we’d end up overly focusing [...] Related

• Fixing the State Machine: Aid Game Repair

  424 readersstrong>Getting the States Straight In a recent post to illustrate the use of composition and delegation, I created a simple game using a State design Pattern—the Aid Game. A lot of people had lots of questions and suggestions for making it better and being one who thrives on improvement and change, I promised to have

• The ActionScript 3.0 Design Pattern Thrill Ride: Part II—Catalyst

  521 readersI’ve been working on a project with Adobe Catalyst, and if I didn’t do something for a Design Pattern tour now, it would be put off until I don’t know when. So I put together a non-design pattern application incorporating video and code snippets from the Aid Game. I simply have not had time [...]

• 

  The ActionScript 3.0 Design Pattern Thrill Ride: Part II—Catalyst

  257 readersI’ve been working on a project with Adobe Catalyst, and if I didn’t do something for a Design Pattern tour now, it would be put off until I don’t know when. So I put together a non-design pattern application incorporating video and code snippets from the Aid Game. I simply have not had time [...] Related

• ActionScript 3.0 State Design Pattern: An Aid Game

  456 readersfter creating the post on the acquaintance relationship between classes, I started thinking about the aggregate relationship and delegation. One of the best examples of delegation can be found in the State design patterns. All of the states are delegated to objects that handle each state. So I thought it’d be a good idea to

• 

  The ActionScript 3.0 Design Pattern Thrill Ride: Part I

  211 readersMy initial idea of having a “thrill ride” through a design pattern to help reveal its operation is turning out to be awkward in more ways than I envisioned. The initial tour is going to be through a State Design Pattern; so naturally I set it up using a State pattern. It wasn’t too long

• ActionsScript 3.0 Design Pattern Relations Part II: Aggregation

  578 readers‘m tempted to say that aggregation is a stronger form of acquaintance, and that wouldn’t be far from wrong. In fact, in certain contexts it may be perfectly correct. Gamma, et al point out that the differences between the two is a matter of intent rather than explicit language mechanisms. That makes it a [...]

• The ActionScript 3.0 Design Pattern Thrill Ride: Part I

  441 readersMy initial idea of having a “thrill ride” through a design pattern to help reveal its operation is turning out to be awkward in more ways than I envisioned. The initial tour is going to be through a State Design Pattern; so naturally I set it up using a State pattern. It wasn’t too long

• ActionScript 3.0 Design Pattern Re-use and Modification

  485 readersvery Monday I have to separate out the paper, glass, aluminum, and plastic to recycle and take them up to the curb. This last Monday while engaged in this weekly ritual, I thought that recycling a design pattern might be an interesting exercise. Additionally, it’s the kind of design pattern advantage that can be used

• 

  ActionsScript 3.0 Design Pattern Relations Part IV: Creation

  164 readersne of the least discussed relations in Design Patterns is where one participant creates an instance of another. Basically, the pattern calls for one class to instantiate another class. This relationship is indicated by a broken line with an arrowhead pointing to the class that has been instantiated. (The Participant Relations diagram above shows