Hi Chris,
I don't know if it's feasible, but perhaps a custom
PersistentFieldStrategy that uses cookies would do the trick?
http://tapestry.formos.com/nightly/tapestry5/apidocs/org/apache/tapestry/services/PersistentFieldStrategy.html
-Filip
Chris Poulsen skrev:
Hi,
Josh Canfield wrote:
Hi Chris, check out
http://tapestry.apache.org/tapestry5/tapestry-core/guide/mixins.html
You could implement the hypothetical "DefaultFromCookie" mixin.
Josh
Yes, that seems like it was intended for something similar to what I'd
like to do. I haven't looked deeply into the mixins, but I'm pretty sure
that they provide the bits i need in order to "load" the default from a
cookie.
I would also like to make the "save" of the cookie values happen in this
manner. But currently I'm a bit lost on how to trigger the code that
saves. Perhaps "event bubbling" does make certain of the form related
events available in the component, but if I understand the "one liner"
documentation the events are propagated from components towards the
page, not the other way around??
As I think I've read that the Form component "instructs" its components
to retrieve values and perform single field validation, I'm pretty sure
that there are some events going "into" the components, I just haven't
been able to figure out how to listen for them.
Could some1 offer an explanation of how the build in "Field" components
does their validation etc. or perhaps an example ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
