Re: Undo logic location?
Re: Undo logic location?
- Subject: Re: Undo logic location?
- From: Jim Correia <email@hidden>
- Date: Thu, 6 Jan 2005 13:36:43 -0500
On Jan 6, 2005, at 1:05 PM, mmalcolm crawford wrote:
On Jan 6, 2005, at 6:12 AM, Jim Correia wrote:
Aaron's example is fairly simply in terms of the model. A flag list
of Persons, each with two properties. The observer method for undo
doesn't feel like it would scale well to more complicated models,
perhaps with more properties, and objects that themselves contained
arrays of different model objects.
The pattern Aaron describes is effectively the same as that employed
by EOF -- which scaled well enough...
Perhaps I wasn't clear. I didn't mean scale in the falls down at
runtime sense, I meant scale in the development sense: the amount of
logic and knowledge of the underlying models that has to be known and
accounted for at the model-controller level. If the model objects are
really supposed to encapsulate their data and implementation, it seems
counter to have to have the model-controller level know about all this
information so it can watch for changes and do undo handling. It seems
that the complexity of this setup might get overwhelming when the model
controller has to deal with many different kinds of model objects, each
with many properties. (IOW, if a model object gets a new property, I
not only have to update the model object - which is a given, but I have
to go to all the model-controller level objects, and let them know
about that property so they can handle undo for me.)
Are you saying that in real work EOF applications, this "maintenance
burden" didn't really exist?
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden