It doesn't matter if it's a collection of dumb value objects, a
component, a state variable, or just a common effect. If an object
is used more than a couple of times in the app, put it in the
ModelLocator. Remember, everything is an object; instantiated and
destroyed like the rest of them
My question isn't about the model locator. It's about logic, or lack
thereof encapsulated within the domain objects.
On 05/12/2006, at 9:59 PM, Tim Hoff wrote:
It doesn't matter if it's a collection of dumb value objects, a
component, a state variable, or just a common effect. If an object
2 matches
Mail list logo