On 8/11/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > Its not that I don't trust the user, the point is to automate the 90% use > case which is to have something happen after the default form processing > updates your model. > > The internalOnClick will be finalized. So if you don't want default form > processing you extend from Button, and if you do want it you extend from > SubmitButton and onclick in that class gets called AFTER the form has been > processed and model updated.
ABS is good but I still prefer to change gears myself. On 8/11/05, Jonathan Locke <[EMAIL PROTECTED]> wrote: > i just can't follow this discussion any more. please let me know when > everyone agrees so i can think and/or vote on the proposal. I cannot argue anymore, too :) I do not like all these internal methods and hiding, but I can live with it. 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
