Naftoli Gugenheim naftoli...@gmail.com writes:
What would such an abstraction do?
What code would you like to write (including templates) and what should it do?
I had some input here:
Indeed, if you're building a lot of forms, you quickly realize that Lift
currently requires fair amount of code for forms that are not backed by
mapper elements. There's space there for better abstrations / DSL
improvements to reduce boilerplate -- similar to what David has built for
the new
What would such an abstraction do?
What code would you like to write (including templates) and what should it do?
-
Alex Boisvertalex.boisv...@gmail.com wrote:
Indeed, if you're building a lot of forms, you quickly realize that Lift
currently requires fair
I think the idea is to be a little more declarative on defining the form and
separate the low-level concerns of handling all the events to a more generic
form handler,
object ShipToForm extends Form {
val name = Variable[String](customerName)
val address1: Variable[String]()
val address2:
I think I have to split the wizard stuff out so you can declare a single
screen with validation.
On Thu, Dec 17, 2009 at 11:23 AM, Alex Boisvert alex.boisv...@gmail.comwrote:
I think the idea is to be a little more declarative on defining the form
and separate the low-level concerns of
Hello lift people,
lift seems very promising. I am trying to make some tests
and examples because I am new to lift.
I wanted to add some validation to a form element and show
the validation error to the user.
But after little searching I was a little disappointet to see that
there
is no such
