On 8/11/05, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > michael's message was confusing to me. i wasn't sure if he was talking > about forms or buttons. > or really what his original problem was.
I am sorry, I was talking about buttons. > what is it that we gain here michael and what exactly is the proposal? > i still don't quite understand > what you're getting at in terms of the current functionality. how > exactly would you change it? Um, all I was trying to say is that I would prefer to have well defined event sequence (I guess, for a form in this case), which is wrapped in one method like process() or something, which is called automatically now. In this case I would call either this process() method as a whole, or smaller fine-grained methods which comprise process() method, from my onSubmit() handler *for a button*. See another message for onClick(). On the other hand, form processing in its current state *does not bother me that much* ;-), so if I can simply turn off default processing, this will work as well. I am sorry that I was not clear. Forget the whole thing :) Michael. P.S. isImmediate() is ok imho, since it is already used in JSF. And I suppose that Wicket wanted to support JSF components anyway. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
