Jeppe, Very interesting stuff - agree with most of your points, however, this statement:
"While you can’t get code into your templates, it’s easy to get UI into your code, which is (almost) just as bad. The dynamic part of the UI is done by snippets and they of course need to emit HTML. But it is easy to put all kinds of style, class attributes as well as other things which belong in the template, into this dynamically generated code. This makes it difficult for designers to modify the layout and styling without touching the Scala code." I think this generally goes back to developers being pretty lazy in general; that is, the path of least resistance is the easier option rather than being disciplined in their coding. What would you suggest from your experience could be a solution for this? It seems the solution would be to make it easier to "do the right thing" rather than use xml literals and make bad code, but *how* could this actually be done in a meaningful way? Cheers, Tim On Jan 18, 8:44 pm, Jeppe Nejsum Madsen <[email protected]> wrote: > Hi, > > A while ago, I started writing an experience report on using Scala & > Lift. I finally finished this (it has been a little more than 6 months > now, time is flying :-) > > http://jeppenejsum.wordpress.com/2010/01/18/scala-and-lift-status-aft... > > /Jeppe
-- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
