I've been looking at the Scala code recently and have found a series of classes that contain a large amount of HTML Code (for example, snipper/UserSnip.scala<http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/main/scala/org/apache/esme/snippet/UserSnip.scala?view=markup> which contains code to display followers and followed amongst other things) . There are some classes - such as ActionView.scala<http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/main/scala/org/apache/esme/view/ActionView.scala?view=markup> - where the hard-coded HTML is even more prevalent.
This tight coupling of HTML and Scala/lift code may make it difficult for those wishing to contribute/patch a specific UI element to know exactly where/how to do so. What about another option where JSON streams are being produced by the Scala code on the server and then the UI developer could decide what technology to use to display the data. At the present time, use of cool UI technology (such as JQuery) is difficult / impossible to use on many screens (Actions, Tracks, etc.) D.
