[
https://issues.apache.org/jira/browse/WICKET-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1127.
-----------------------------------
Resolution: Won't Fix
those overridable factory methods you use in your patch exist for this exact
case - let you customize the palette. i dont see why button components should
be the default implementation as opposed to what there is now. like you did,
you can always customize it.
> Using Buttons in Palette component
> ----------------------------------
>
> Key: WICKET-1127
> URL: https://issues.apache.org/jira/browse/WICKET-1127
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.2.6
> Reporter: Volodymyr Sobotovich
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.3.0-rc2
>
> Attachments: patch.java
>
>
> 1. It would be more convenient to use component Button instead of
> WebMarkupContainer for "add", "remove", "up" and "down" buttons. It will
> allow user to enable or disable them and update via ajax.
> 2. It would be nice to store these buttons as protected members of Palette to
> give subclasses access to them.
> For the workaround been used to gain the functionality see attachment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
