[
https://issues.apache.org/jira/browse/WICKET-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526109
]
Sam Hough commented on WICKET-940:
----------------------------------
Again in the spirit of further documenting one, minority, point of view:
AjaxTabbedPanel seems like a symptom of raising Ajax issues to such a high
level. The TabbedPanel should be busy worrying about being a tabbed panel not
how to behave for Ajax.
Presumably the non-fallback AjaxLink and AjaxButton are deprecated but it still
means you have the Ajax and non-Ajax flavours of components. If buttons and
links came from a factory and had the same signature you would only need one
TabbedPanel and then any extensions via inheritance wouldn't need duplicating.
AjaxTabbedPanel also invents its own hook onAjaxUpdate which also seems ugly.
> 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.
