On Wed, Jul 1, 2009 at 12:04 PM, sjtirtha <sjtir...@gmail.com> wrote:
> > Hi, > > I just started using Lift. > Somehow, I got the feeling that Lift is over lean. > In a Model Class, you can define every thing, from which validation to > which field should appear in UI. > Isn't it contradiction with the concept of "separation of concern" You're assuming the separation of concerns is a good thing. In my 14+ years of writing web apps, I've found that 99% of the time, the model should have the validation rules for fields as part of the model. 80%+ of the time, the model and fields should have a reasonable default for display and user interaction. There's nothing that forces the use of the default display or user interaction methods, but having them close is very, very helpful. Also, please see http://blog.lostlake.org/index.php?/archives/19-Keeping-the-meaning-with-the-bytes.html > > > Regards, > Steve > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
