[
https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169138#comment-15169138
]
ASF subversion and git services commented on ISIS-993:
------------------------------------------------------
Commit 48fe231be5f2946d81eb2192ebfbdd958bbe21a6 in isis's branch
refs/heads/ISIS-993 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=48fe231 ]
ISIS-993: fixes to prevent SpecificationCacheDefault from getting out-of-whack
(by mapping ObjectSpecId to className, rather than spec; can then use the
className to look up the spec in turn).
This stuff came about because reloading of grid after change was only working
if invalidated the class spec (= refresh twice).
> Show different object members on multiple tabs
> ----------------------------------------------
>
> Key: ISIS-993
> URL: https://issues.apache.org/jira/browse/ISIS-993
> Project: Isis
> Issue Type: New Feature
> Components: Core, Core: Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 1.12.0
>
>
> 4-jan-2016:
> Divide the screen into two halves.
> All properties in separate tabs.
> Each collection in its own tabs.
> ~~~
> as per [1] mailing list thread.
> The example in the mailng list splits up the object's properties/collections
> (contributed or otherwise) into two different sets of tabs... but as a first
> pass I think a single row of tabs ought to suffice.
> We also need to be mindful that we may want to use tabs as a metaphor for
> multiple opened objects (as a replacement for bookmarks), so this is another
> reason for a single row of tabs.
> To support this would require extensions to @DomainObjectLayout or equivalent
> xxx.layout.json file.
> [1] http://markmail.org/message/merftvqoiy6ht3kq
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
