[Lift] Re: How forms work (the life cycle of request)

2009-05-11 Thread erik.karls...@iki.fi
> Give me a week or some and I think I'll have something that you'll like... > basically, you can register a function that's called when stuff is added to > the function table... and there'll be a "why" associated with the adding. > When you're running in test mode, you can intercept the functions

[Lift] Re: How forms work (the life cycle of request)

2009-05-11 Thread David Pollak
On Mon, May 11, 2009 at 10:28 AM, erik.karls...@iki.fi < erik.b.karls...@gmail.com> wrote: > > Hi, > > Scala supports true closures which means that variables in scope > (including > > "this") are bound to the function. > > > > Lift associates the function passed to SHtml.text(defaultValue, > > pa

[Lift] Re: How forms work (the life cycle of request)

2009-05-11 Thread erik.karls...@iki.fi
Hi, > Scala supports true closures which means that variables in scope (including > "this") are bound to the function. > > Lift associates the function passed to SHtml.text(defaultValue, > passedFunction) with a GUID and returns places that GUID in the name > attribute of the generated HTML eleme

[Lift] Re: How forms work (the life cycle of request)

2009-05-10 Thread David Pollak
On Sun, May 10, 2009 at 1:35 PM, erik.karls...@iki.fi < erik.b.karls...@gmail.com> wrote: > > Hi, > > I'm asking some questions again :) This time it is about form > handling. I tried to get the idea from source code but I think it > would be easier if some one wiser could open it a bit. > > Here