in reply to A Concise Example of MVC

You have some view IN your controller. Your view objects are to have complete control over how the view works. Your controller has view data in it. Your view objects contain that and the logic for dealing with the model. Edit: Heh, you got some V in your C! I know, back to my hole...

Replies are listed 'Best First'.
Re^2: A Concise Example of MVC
by eric256 (Parson) on Feb 22, 2007 at 15:21 UTC

    Do you mean to say that he should have two separate views? One for web output and one for command line output? Then his control could be simplified even more.


    ___________
    Eric Hodges
[reply]
      Correct. The trick here is, the controler and model should be fairly static if you were presenting the same data via XML, HTTP+SOAP, HTTP+HTML, CLI etc. Then either your controller pushes the data to the view you somehow get a handle of, or the view pulls from the controller (through to the model) the data to present.

      Same is true of the model. If your view and controller stay the same, your model should be fairly possible to replace without too much rigmarole

[reply]
Re^2: A Concise Example of MVC
by Anonymous Monk on Jan 22, 2009 at 13:42 UTC
    Sometimes a bad example is worth more than a good one it seems. (I am aware that vagueness is its own reward.) True: Some V is in the C.
[reply]

In Section Meditations