At 12:49 PM 4/25/2001 -0500, Ian Bicking wrote:
>Isn't the MVC paradigm that the view (i.e., HTML reprsentation) be
>seperated from the model (i.e., Python objects and datastructures).
>Not that one is necessarily more complex than the other. It's the MCV
>distinction that makes me feel like formatting data as English should
>be done in the view, i.e., template.
I used MVC in NeXTstep and even there it was common to add "display"
methods to data objects, *via categories* (which are Obj-C's version of
mix-ins). So again you had separation of concerns, but you also had OOP. If
you wanted an object to draw itself, you sent it the message telling it to
do so. Consequently, subclasses could override this.
If you wanted to write a command line util using the data objects, you
didn't end up loading the drawing code.
Without that approach, subclasses can't customize and you end up building
if-else ladders for different types of objects. That gets ugly fast.
Of course, NeXTstep still had View classes. They were responsible for
various things like mouse clicks, containing subviews, determing their