On 8/11/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> If we decide to break all backwards compat, how about
>
> Button {
> onclick() {
> }
> }
>
> And
>
> SubmitButton {
> onclick() { getform().process(); }
> onsubmit() {} <-- called by form after form processing
> }
>
> So after the form is submitted the processing goes directly to the button
> instead of the form, the button decides whether or not to invoke the default
> processing of the form.
I like this one. It is simple, and I see what is happening and where
it is happening. Debugging will be really simple, just set breakpoint
on onclick() and step from there.
What is the onsubmit() for, why it should be a callback again?
Michael.
-------------------------------------------------------
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
