This reminds me somewhat of the Wicket approach, which would use a namespaced attribute of the <textarea> tag to inform the binding logic. I've been wanting to keep the styling of my lift-generated tags in the markup as well, so maybe I'll toy a bit with creating a version of bind() and the form generator functions that would allow this.
Kris On Wed, Jun 17, 2009 at 11:22 AM, Matt Williams<[email protected]> wrote: > > I wholeheartedly agree with the philosophy of separating the display > from the program logic, and am currently getting to grips with the > generators, but am finding that now I end up with a degree of markup > within my code. > > Can you think of any caveats to infering the node type passed, and > dynamically using the relevant generators to construct the returned > node. > > I am thinking something along the lines of: > > <person:biography> > <textarea style="myStyle" cols="20" rows="5"> > This is a sample of some biography text > </textarea> > </person:biography> > > Where it would automatically infer that it is a textarea, pass through > the relevant attributes, and insert whatever function, values, etc I > have specified in my snippet. > > What are your thoughts on this? > > Brgds, > > Matt > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
