[ 
https://issues.apache.org/jira/browse/ISIS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440516#comment-16440516
 ] 

ASF subversion and git services commented on ISIS-898:
------------------------------------------------------

Commit a8c547dc2546fb73c2a82bb46e8de28c8473e8b2 in isis's branch 
refs/heads/dev/2.0.0/ISIS-898-treeview from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=a8c547d ]

ISIS-898 refine TreeNode interface

> Add a table tree view to the Wicket viewer.
> -------------------------------------------
>
>                 Key: ISIS-898
>                 URL: https://issues.apache.org/jira/browse/ISIS-898
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core: Viewer: Wicket
>    Affects Versions: viewer-wicket-1.6.0
>            Reporter: Dan Haywood
>            Assignee: Andi Huber
>            Priority: Minor
>             Fix For: 2.0.0-M2
>
>
> see mailing list discussion [1]
> [1] http://markmail.org/message/vu3jqmlawrskplic
> ~~~
> some further thoughts:
> 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
(v7.6.3#76005)

Reply via email to