[
https://issues.apache.org/jira/browse/WICKET-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525892
]
Sam Hough commented on WICKET-940:
----------------------------------
I'm not really trying to change your mind just add a note about how at least
one developer wanted to use Wicket.
Our application code uses OurButton which extends AjaxFallBackButton which
removes the need to call super and hides AjaxRequestTarget.
As I've said before I'm new to Wicket world but AjaxRequestTarget does seem
pretty low level to me. I'm really pleased to move away from thinking in just
strings (as with JSP etc) and move higher up the abstraction food chain to
components. Wicket does this really nicely. It may just be the drugs but I
don't see the need to manage component updates by hand.
Anyway, might give me just enough of an excuse to have handler objects rather
than re-implementing onClick etc. I've still not come up with a nice way to
tell ListChoice etc that I want the server to be notified of events. Presumably
be more familiar to people coming from Swing or GWT etc...
Cheers Igor ;)
> AjaxFallbackLink.onClick be helpful if not final
> ------------------------------------------------
>
> Key: WICKET-940
> URL: https://issues.apache.org/jira/browse/WICKET-940
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Reporter: Sam Hough
> Assignee: Igor Vaynberg
> Priority: Minor
>
> I'd like to override AjaxFallbackLink.onClick and have application code live
> there rather than in the Ajax specific method. Obviously I could have
> onMyClick but this seems rather ugly and wouldn't look/feel the same as just
> using a Link object.
> AjaxFallbackButton.onSubmit is not final so it also seems inconsistent.
> Thanks
> Sam
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
