It depends on your abstraction composition. Typically, I make sure that my business logic is separate from UI logic... this is just good design; its possible to abuse any tool or framework if you have no idea about proper software engineering. I wouldn't worry too much about that - the pattern itself is far cleaner than MVC.
Cheers, Tim On 5 Mar 2010, at 14:21, Julian Backes wrote: > Thank you for your answer, also thanks to Jeppe who posted the same solution. > > > I disagree with the unglyness you are talking about just because > > Snipets are UI elements. > I already read that and although I don't want to start a discussion on this, > I want to share my opinion with you: > I already read in some blog entries and also here on the mailing list that > lift completely avoids the problem of having business logic in your > views/templates. > I think in general, this is a very good idea. On the other hand, many people > say snippets are part of the view. In almost all examples I found, you can > see business logic in the snippets. Is this really better now? I think you > are still mixing business logic and UI stuff, just on a different level. Of > course, you can seperate that but this adds unnecessary complexity to an > application. > Or am I missing something? I'm still a beginner in the scala/lift world... :-) > > Julian > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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. > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
