> Well, we are doing something very similar. Because there are so many > potential exit points from some of our form pages, we use the onchange > action of the form elements rather than the onclick action of the
While we're talking about onChange: Unfortunately it's not possible to add onChange/onLoad/etc javascript triggers to a PropertySelection. It doesn't support informal parameters. I know there's no direct mapping from a PropertySelection (at least with this "abstract name") but it's very bad this way. I had to install my own PropertySelectionRenderer and access generateAttributes() from it to render attributes too, and because generateAttributes() is protected and not accessible from my package I had to put my renderer in net.sf.tapestry :-) Howard, any chance for allowing us to add informal parameters to PropertySelection? And don't you think methods such as generateAttributes should be placed in a RenderingUtil class? Ara. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
