You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Adam Greene <ag...@professionalopensource.ca> on 2005/09/03 07:16:04 UTC
Form.addEventHandler deprecated without clear replacement
What is the expected replacement for Form.addEventHandler. I know it has to do with FormComponentContributor and FormComponentContributorContext, but how does one use them?
Re: Form.addEventHandler deprecated without clear replacement
Posted by Adam Greene <ag...@iq-2000.com>.
So if I wanted to add a FormSub handler in the new way from within a
component that does not use validators or translators, how would I do so?
----- Original Message -----
From: "Howard Lewis Ship" <hl...@gmail.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Saturday, September 03, 2005 11:04 AM
Subject: Re: Form.addEventHandler deprecated without clear replacement
I hope to document this soon.
You now "manage" the event listeners for a Form on the client side.
Client-side Forms now have an "errors" property of type
FormEventManager (remeber, this is all JavaScript). See Form.js. You
can register an event handler for a form ... there's a multitude of
types of listeners basically tied into the normal submit (with
validation), refresh, and cancel forms of requests.
FormComponentContributorContext streamlines the process of generating
this JavaScript. It is primiarly used by Translator and Validator
implementations.
On 9/3/05, Adam Greene <ag...@professionalopensource.ca> wrote:
> What is the expected replacement for Form.addEventHandler. I know it has
> to do with FormComponentContributor and FormComponentContributorContext,
> but how does one use them?
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Form.addEventHandler deprecated without clear replacement
Posted by Howard Lewis Ship <hl...@gmail.com>.
I hope to document this soon.
You now "manage" the event listeners for a Form on the client side.
Client-side Forms now have an "errors" property of type
FormEventManager (remeber, this is all JavaScript). See Form.js. You
can register an event handler for a form ... there's a multitude of
types of listeners basically tied into the normal submit (with
validation), refresh, and cancel forms of requests.
FormComponentContributorContext streamlines the process of generating
this JavaScript. It is primiarly used by Translator and Validator
implementations.
On 9/3/05, Adam Greene <ag...@professionalopensource.ca> wrote:
> What is the expected replacement for Form.addEventHandler. I know it has to do with FormComponentContributor and FormComponentContributorContext, but how does one use them?
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org