tapestry-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: Form.addEventHandler deprecated without clear replacement
Date Sat, 03 Sep 2005 14:04:20 GMT
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 <agreene@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


Mime
View raw message