Re: Question about MVC
Re: Question about MVC
- Subject: Re: Question about MVC
- From: George Orthwein <email@hidden>
- Date: Wed, 26 Apr 2006 11:27:13 -0400
MVC doesn't mean the View can't talk to the Controller, it just means
that you don't want the View and the Model communicating directly.
M<-->C<-->V
As you pointed out, the View has to tell something that the user has
clicked/typed/interacted with the App! :)
George
On Apr 26, 2006, at 8:39 AM, Kenny Millar wrote:
I.S,
That's an interesting reply, and I understand exactly your point of
view.
However I too am currently pondering an MVC design, where I can't
think of
any other way but by having the view maintain an instance variable
of the
controller... let me explain.
My data contains a set of objects, which the view renders to the
screen.
When the user clicks in the view, whichever object he clicked on
becomes the
'current' object, and the controller needs to know which is the
'current'
object. How can you do that without the view telling the
controller, and how
can the view tell the controller without either i)using a delegate, or
ii)maintain an instance variable and sending messages to the
controller?
Maybe I just haven't grasped the full MVC picture yet, but I'm just
a newbie
so willing to be shown the right direction!
-Kenny
_______________________________________________
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