Don't forget LinkSubmit. :-) Also, what do you think about some of the other ideas? 1) Conistent parameters for all listeners, where the developer can choose whether the parameters are encoded in the URL (like DirectLink "service parameters") or computed during the rewind (like component properties). (This idea is basically an extension of your "Improved Listener Methods in Picasso" blog from April 13th.) 2) Consistent multiple event listeners for various components (such as an "onChangeListener", an "onFocusListener", etc.), with the "defer" option and parameters for every listener.
Even if these are good ideas, I realize that they probably wouldn't make it into 4.0, and some are component enhancements as opposed to framework enhancements. But does anybody else have any thoughts on these? Like? Dislike? For what its worth, I was just now reading a thread from back in May 2004 (in the dev mailing list archives) about delayed listeners. ...they say everything old is new again. :-) -Nathan Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > I've just added a "defer" parameter to Submit and ImageSubmit. > > Once Tapestry automatically handles everything, there'll be a lot less > for me to cover in my labs! > > On 5/9/05, Nathan Kopp <[EMAIL PROTECTED]> wrote: > > "Nathan Kopp" <[EMAIL PROTECTED]> wrote... > > > > > (*Note: I'm not totally sure, but I think that with listener parameters, > > > the immediate-firing listeners would probably be unnecessary. Comments?) > > > > Commenting on my own thoughts (this won't make any sense unless you've read > > the original email completely).... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
