tags:

views:

39

answers:

0
Q: 

Alternatives to this development pattern

Usually I start with pure model objects, usually in a tree structure.

Depending upon the application, I will end up adding functionality to the model heirarchy, such as attaching UI controls and other data depending upon the application.

Usually I'll do this by walking through the heirarchy and placing additional functionality on the model object by wrapping it.

So I end up with the model heirarchy being accessible from two different places: the pure model heirarchy and the "decorated" model heirarchy.

Is there any alternative to this?

related questions

How to keep track of the references to an object?
When should you use 'friend' in C++?
Overiding the equals method vs creating a new method
Making one interface overwrite a method it inherits from another interface in PHP
What are the correct stencils for object relational diagramming in visio?
Is Single Responsibility Principle a rule of OOP?
Expression Evaluation and Tree Walking using polymorphism? (ala Steve Yegge)
Access to global application settings
Inheritance and Polymorphism - Ease of use vs Purity
Do you name controls on forms using the same convention as a private variable?
How do you create a static class in C++?
How do you create objects in Perl?
Why all the Active Record hate?
When is OOP better suited for?
Accessing a CONST attribute of series of Classes
Multi-Paradigm Languages
Speed Comparisons - Procedural vs. OO in interpreted languages
pass by reference or pass by value?
How to Think in OO
Using object property as default for method property
Adding a Method to an Existing Object
Object Oriented vs Relational Databases
Class views in Django
C++: Should I use nested classes in this case?
How would you access Object properties from within an object method?