I'd suggest pulling all the code out of the various ProtoUser code and rolling it into the User code in the ESME code base such that User extends LongKeyedMapper[User] That will give you maximum flexibility in terms of getting the view code out of the Scala code and into templates.
On Tue, Apr 28, 2009 at 7:35 AM, Richard Hirsch <[email protected]>wrote: > Here are the JIRA items: > > https://issues.apache.org/jira/browse/ESME-60 > https://issues.apache.org/jira/browse/ESME-61 > https://issues.apache.org/jira/browse/ESME-62 > https://issues.apache.org/jira/browse/ESME-63 > > D. > > On Mon, Apr 27, 2009 at 2:42 PM, Richard Hirsch <[email protected] > >wrote: > > > They've already been found. Just have to create individual JIRA items. > > > > D. > > > > > > On Mon, Apr 27, 2009 at 1:21 PM, Darren Hague <[email protected] > >wrote: > > > >> Hi Dick, > >> > >> Feel free to raise these as JIRA tickets and assign them to me as you > find > >> them. I agree that moving HTML out of the Scala source is a Good Thing > (TM). > >> > >> Cheers, > >> Darren > >> > >> >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/m > >> >ain/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. > >> > >> > >> > >> -- > >> [email protected] > >> > > > > > -- 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
