e onchange="javascript:tapestry.form.refresh(formName)"
Thanks,
Greg
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 20, 2006 2:54 PM
To: Tapestry users
Subject: Re: Radio components
http://tapestry.apache.org/tapestry4.1/javascript/form.html
&&
http://tapestry.apache.org/tapestry4.1/javascript/form.html
&&
http://tapestry.apache.org/tapestry4.1/usersguide/upgrade4.0.html
(the last one is a work in progress)
On 12/20/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Whatever happened to adding
onchange="javascript:this.form.events.ref
Whatever happened to adding
onchange="javascript:this.form.events.refresh();"
to a Radio component in 4.1? Documentation doesn't mention the new method,
hoping there is one :(
Thanks,
Greg
-
To unsubscribe, e-mail: [EMAIL PROT
"Indirectly" implies that the RadioGroup and Radio components might not
reside in the same page or component. For instance a RadioGroup might be
in the page template, and a number of other components wrapped by it might
contain Radio components. These are wrapped "indirectly".
Joseph Hannon <[EMAIL PROTECTED]> wrote:
Anyone?
jah.volcano wrote:
> Page 112 of 'Tapestry in Action' mentions that radio components must be
> enclosed by RadioGroups but don't need to be directly enclosed- they can
> be scattered about the html. Nice feature but no e
Anyone?
jah.volcano wrote:
Page 112 of 'Tapestry in Action' mentions that radio components must be
enclosed by RadioGroups but don't need to be directly enclosed- they can
be scattered about the html. Nice feature but no explanation or example
given. Will someone show a si
Page 112 of 'Tapestry in Action' mentions that radio components must be
enclosed by RadioGroups but don't need to be directly enclosed- they can
be scattered about the html. Nice feature but no explanation or example
given. Will someone show a simple example of html tha
