[
https://issues.apache.org/jira/browse/ISIS-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244377#comment-14244377
]
Martin Grigorov commented on ISIS-979:
--------------------------------------
Seems to be related to ISIS-898
> Provide a new widget for collections to render hierachies in a tree-table.
> --------------------------------------------------------------------------
>
> Key: ISIS-979
> URL: https://issues.apache.org/jira/browse/ISIS-979
> Project: Isis
> Issue Type: New Feature
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.9.0, core-1.9.0
>
>
> For example, in Estatio there are several hierarchies
> EstatioInstance ("global") /
> EstatioInstance ("italy") /
> EstatioInstance ("Roma shopping mall")
> or:
> Property/
> Floor/
> Unit
> We'd like to render these objects in a single tree/table collection.
> ~~~
> We should distinguish two cases:
> - where all the rows are of the same type (EstatioInstance, turtles all the
> way down).
> - where all the rows are of different types (Property/Floor/Unit)
> For the former, the columns to use are exactly those of the (single) class.
> For the latter, things are more complicated, as all the objects are of
> different class. It's not clear to me what (apart from an icon and a title)
> should be shown as columns. Perhaps just the intersection of those
> properties that are common across all types (eg name?) . Or perhaps there's
> metadata (in @PropertyLayout(...)) to specify that a particular property
> should always be shown in such tree/table collections, even if it is null for
> other rows for instances of some other class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
