[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-24 Thread Charles F. Munat
Charles F. Munat wrote: Running Ajax calls between fields for validation is pretty ugly, javascript validation would be better That's what I said. Sorry, Oliver. On re-reading, that sounds a little snippy, but I didn't mean it that way. I just meant that we agree -- after mentioning it as

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-24 Thread Oliver Lambert
Hey Chas, No worries, I re-read too and understood the tone of your reply. I'm playing devils advocate on validation to try to get a flexible framework for everyone to use. Ol On 24/09/2008, at 4:07 PM, Charles F. Munat wrote: Charles F. Munat wrote: Running Ajax calls between fields for

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-23 Thread David Pollak
Marius wrote: I'm fully aware of that ... I was just wondering if there were other rationales behind this approach ... or we can have trait Foo[T : Foo[T]]) { self: T = def dog(t: T) = t.doSomething def doSomething } Sorry for being clueless... but I'm not sure what the

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-23 Thread Derek Chen-Becker
If you want to tell them to enter a value, I'm sure that you could write (if it doesn't already exist) a notEmpty validation that would say the right thing and do something like: val validations = notEmpty(You must provide an email address) _ :: valRegex(... Derek On Tue, Sep 23, 2008 at 9:41

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-23 Thread David Pollak
Derek Chen-Becker wrote: If you want to tell them to enter a value, I'm sure that you could write (if it doesn't already exist) a notEmpty validation that would say the right thing and do something like: val validations = notEmpty(You must provide an email address) _ :: valRegex(...

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-23 Thread David Pollak
Charles F. Munat wrote: Oliver Lambert wrote: Do/should validations stop at the first error message on the field, at least by default? I much prefer that they do not. It really irritates me when I'm using an online form and it tells me that something is invalid, then I fix it,

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-23 Thread Charles F. Munat
http://liftweb.net/index.php/RequirementsForForms David Pollak wrote: Charles F. Munat wrote: Oliver Lambert wrote: Do/should validations stop at the first error message on the field, at least by default? I much prefer that they do not. It really irritates me when I'm using

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

2008-09-23 Thread Charles F. Munat
Oliver wrote: I like them to be validated as well, and to short circuit the remainder of the field validation. Feel free to set your validation up that way. Personally, I'd like my validation code to be smart enough to note when two non-redundant validation problems occur and to mention