Exactly, an object should know how it's surface reflects light, not some view-crap on the side of it.
Honestly I think people advocating MVC (or MVC2, or any of the inbred MVC siblings) have never tried anything else. It's like those who refrain from using inheritance in their JPA models. Why use OO at all if everything you use are structs on steroids? Just my 2 cents! :) Kram! On Sun, Jan 4, 2009 at 5:58 PM, Michael <mike...@gmail.com> wrote: > > > Also I was looking at the sample model source code (User, ProtoUser) > > and saw presentation logic mixed in it. Shouldn't the business and > > model logic be kept separated from the presentation logic or is there > > a Lift strategy it? > > Hmm, a model that can render itself ... That sounds like this crazy > paradigm called object-oriented programming. Some radicals say it has > some advantages over the more procedural style of MVC. > > -- Michael > > > > -- Viktor Klang Senior Systems Analyst --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
