[
https://issues.apache.org/jira/browse/WICKET-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483265#comment-13483265
]
William R. Speirs commented on WICKET-4828:
-------------------------------------------
I see your point, but would argue that someone asking for 2 details rows could
implement that as they can put any component (even another DataTable) inside
the details row. As for the other col span, would it be more appealing for me
to provide methods to tweak how that work? I figured people who wanted those
types of changes would simply extend the class and override the method.
That code snipit did make me cringe just a bit when writing it, but I couldn't
find another more elegant way... any thoughts?
In the end, I was looking to make a component that would provide usefulness in
90% of the use cases and provide an example of how to implement such a
component if you had other needs such as different colspan, more detail
columns, etc...
> DetailsTable Implementation
> ---------------------------
>
> Key: WICKET-4828
> URL: https://issues.apache.org/jira/browse/WICKET-4828
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-extensions
> Affects Versions: 6.2.0
> Reporter: William R. Speirs
> Priority: Minor
>
> This ticket is to add a new type of table to wicket-extensions, the
> DetailsTable. A details table provides an additional row for each table row
> which provides details about the row above it. The details row can be
> shown/hidden via a component in a table column.
--
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
