P-Patterns!
From Andrey
(Difference between revisions)
| Revision as of 20:09, 6 February 2006 Andrey (Talk | contribs) ← Previous diff |
Revision as of 20:13, 6 February 2006 Andrey (Talk | contribs) Next diff → |
||
| Line 3: | Line 3: | ||
| == Golden Bridge == | == Golden Bridge == | ||
| - | Utilizing the Bridge design pattern for separating model from application-specific behaviors. | + | Utilizing the Bridge pattern in order to separate model from application-specific behaviors. |
| + | |||
| + | == X class == | ||
| + | |||
| + | Divide model classes into pure and application-specific classes, in the model, use only pure classes, but in application, instantiate only application-specific classes. | ||
| == Smart Button == | == Smart Button == | ||
Revision as of 20:13, 6 February 2006
Some stuff that I came up with.
Contents |
Golden Bridge
Utilizing the Bridge pattern in order to separate model from application-specific behaviors.
X class
Divide model classes into pure and application-specific classes, in the model, use only pure classes, but in application, instantiate only application-specific classes.
Smart Button
Expose a generic object in the interface in order to simplify class use.
Postponed Validation
Postponing validation until checkpoint/commit so that validations do not hinder performance.
Pascal example.
