View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Discussion 2 - Daniel Kitchener

What is Portland Form:

Portland form is a way of describing design patterns. Unlike most other ways of describing design patterns, the Portland Form is a narrative way, which is quite a bit easier to understand than just an outline. There are 3 parts of Portland Form. The Language Document shows how the patterns are linked, and the Pattern Paragraph describes the pattern in the form of first presenting a problem then describing how the pattern solves it. The Summary Section groups patterns together by the problems they solve.

URL: Couldn't find anything else halfway decent on google, so it's just the site y'all gave us:

Describe an Interesting Pattern:

Well, to be honest, none of them really "interest" me. I'm not that easily entertained. However, one that does seem a little different from the norm, yet still useful is the Memento design pattern, which captures and stores an object's internal state. This is pretty cool, in terms of it allowing you to say "hey, let me set a restore point here" so that you can go back to the way things were. It's also implemented in such a way that it doesn't violate the principles of encapsulation, which is great for people who program with true object-oriented design in mind.


Oh, and plus, it also shares a name with one of the most awesome movies of all time:

Link to this Page