You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Rafael Winterhalter (JIRA)" <ji...@apache.org> on 2012/09/19 12:50:07 UTC

[jira] [Updated] (WICKET-4772) DataTable API and handling of AbstractToolbar

     [ https://issues.apache.org/jira/browse/WICKET-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael Winterhalter updated WICKET-4772:
----------------------------------------

    Summary: DataTable API and handling of AbstractToolbar  (was: DataTable API)
    
> DataTable API and handling of AbstractToolbar
> ---------------------------------------------
>
>                 Key: WICKET-4772
>                 URL: https://issues.apache.org/jira/browse/WICKET-4772
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-extensions
>    Affects Versions: 1.5.8
>            Reporter: Rafael Winterhalter
>            Priority: Minor
>              Labels: AbstractToolbar, DataTable
>
> The DataTable API is not optimal from my point of view as a user. What I do today is that I copy-paste most of the data table code in order to break the data table API open. To name a tangible example:
> I implemented a toolbar that applies a filter to each column's values. The updating of the data table's contents is fairly simple by overriding the data table's "newBodyContainer" method, extracting the component and adding it to the AjaxRequestTarget whenever the table is updated. However, this does not affect any of the other 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira