[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194809#comment-15194809 ] ASF subversion and git services commented on ISIS-993: -- Commit 6fa0376873749031bd64b3a34201742b49e6ffa4 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=6fa0376 ] ISIS-993: SizeSpan (one of the grid classes) should be serializable. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186735#comment-15186735 ] ASF subversion and git services commented on ISIS-993: -- Commit 981d731f3642ccbe67c3a8c78c677c1bf1794a4f in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=981d731 ] ISIS-1299: JAXB-annotated view models are now edited. I suspect that ISIS-993 also had broken other directly cloneable view models; anyway, is now fixed. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186729#comment-15186729 ] ASF subversion and git services commented on ISIS-993: -- Commit 1cfb478e022502f0f7ea26dca87bae8094ce5bb6 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1cfb478 ] ISIS-993: fixing the JDK7 re-implementation (which was resulting in spurious top-level actions appearing as top-level) For some reason FluentIterable#transform(...) doesn't iterate as I expected. Replacing with a simple loop. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186728#comment-15186728 ] ASF subversion and git services commented on ISIS-993: -- Commit cf14cead09f73fb3cca051be1fa99427ffb9b2e1 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=cf14cea ] ISIS-993: domain object facets (from grid XML) should overwrite existing facets in metamodel (if present) ... eg bookmarking, naming > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184554#comment-15184554 ] ASF subversion and git services commented on ISIS-993: -- Commit 641ae1508463dedb7088a2166eeaf9d87cfddb67 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=641ae15 ] ISIS-993: recreating simpleapp archetype > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184547#comment-15184547 ] ASF subversion and git services commented on ISIS-993: -- Commit 7805795ba9b87101e7440608514e7050e2ac41fc in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7805795 ] ISIS-993: fixing layout in simpleapp; minor doc change > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184026#comment-15184026 ] ASF subversion and git services commented on ISIS-993: -- Commit 5e0dc0d058702be2cfaee921ae84d939e639613c in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5e0dc0d ] ISIS-993: more docs > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183977#comment-15183977 ] ASF subversion and git services commented on ISIS-993: -- Commit 3b3daa24bf4c67f096fdcc9e6ea6c385ac7d5255 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3b3daa2 ] ISIS-993: further documentation on the layout/grid system. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183981#comment-15183981 ] ASF subversion and git services commented on ISIS-993: -- Commit d57b100245e7e39a5da0d03d393d1d9f66e46788 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d57b100 ] ISIS-993: fixing java7 compile issues. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183978#comment-15183978 ] ASF subversion and git services commented on ISIS-993: -- Commit 9194e136aad5f944374252e411d61b91e12ad41a in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=9194e13 ] ISIS-993: more documentation. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183980#comment-15183980 ] ASF subversion and git services commented on ISIS-993: -- Commit 3b5da6bd73bbd8e1b62670b5bfaebb9e9af87583 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3b5da6b ] ISIS-993: fixing compile issue from stale javadoc ref. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183979#comment-15183979 ] ASF subversion and git services commented on ISIS-993: -- Commit 41a534db984440b3a163a1285e9f397271ecdf8c in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=41a534d ] ISIS-993: more documentation, some minor fixes... fixes: - if first property in a fieldset is invalid (was losing the actions associated with the fieldset). - schema location in downloaded XML was missing the bootstrap3 grid. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183976#comment-15183976 ] ASF subversion and git services commented on ISIS-993: -- Commit 5306b01129faa34e4aef03a1c115db3d801e78e5 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5306b01 ] ISIS-993: split LayoutService back out into LayoutService (API) vs GridService (SPI); rationalizing APIs; adding documentation. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183971#comment-15183971 ] ASF subversion and git services commented on ISIS-993: -- Commit d57b100245e7e39a5da0d03d393d1d9f66e46788 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d57b100 ] ISIS-993: fixing java7 compile issues. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183970#comment-15183970 ] ASF subversion and git services commented on ISIS-993: -- Commit 3b5da6bd73bbd8e1b62670b5bfaebb9e9af87583 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3b5da6b ] ISIS-993: fixing compile issue from stale javadoc ref. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183879#comment-15183879 ] ASF subversion and git services commented on ISIS-993: -- Commit 41a534db984440b3a163a1285e9f397271ecdf8c in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=41a534d ] ISIS-993: more documentation, some minor fixes... fixes: - if first property in a fieldset is invalid (was losing the actions associated with the fieldset). - schema location in downloaded XML was missing the bootstrap3 grid. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183655#comment-15183655 ] ASF subversion and git services commented on ISIS-993: -- Commit 9194e136aad5f944374252e411d61b91e12ad41a in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=9194e13 ] ISIS-993: more documentation. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183654#comment-15183654 ] ASF subversion and git services commented on ISIS-993: -- Commit 3b3daa24bf4c67f096fdcc9e6ea6c385ac7d5255 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3b3daa2 ] ISIS-993: further documentation on the layout/grid system. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182253#comment-15182253 ] ASF subversion and git services commented on ISIS-993: -- Commit 5306b01129faa34e4aef03a1c115db3d801e78e5 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5306b01 ] ISIS-993: split LayoutService back out into LayoutService (API) vs GridService (SPI); rationalizing APIs; adding documentation. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181792#comment-15181792 ] ASF subversion and git services commented on ISIS-993: -- Commit b985845296125bb737df20a55723a10c5ca69ccb in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b985845 ] ISIS-993: tidying up GridImplementationService... specifically: - change lexical order of methods in GridImplementationServiceAbstract, per call hierarchy - only generate a warning if in prototyping mode; also: - if obtaining the complete(...) or the minimal(...) grids, then instantiate a new grid (rather than using the one that might be being cached by GridFacetDefault) because these methods modify said grid object (complete(...) adds stuff, minimal(...) removes stuff). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181767#comment-15181767 ] ASF subversion and git services commented on ISIS-993: -- Commit e55640e2645437ab961a9b873eb159cad7d8fc14 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e55640e ] ISIS-993: rationalizing and simplifying the domain services that support the dynamic layouts. Specifically: - new LayoutServiceMenu (formally was MetadataMenu), now delegates to ... - renamed GridService to LayoutService, simplified and combined methods, but also added downloadLayouts for LayoutServiceMenu to call - renamed GridNormalizerService to GridImplementationService > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180229#comment-15180229 ] ASF subversion and git services commented on ISIS-993: -- Commit fa4c9c1f71766e31171935dc40c0f528359bd09b in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=fa4c9c1 ] ISIS-993: documentation on XML layouts. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178484#comment-15178484 ] ASF subversion and git services commented on ISIS-993: -- Commit e417a8ab5984393394113066a7ad1ea8379bcab2 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e417a8a ] ISIS-993: ensure that actions associated to properties/collections/fieldsets are added in the correct order when normalizing grid. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178494#comment-15178494 ] ASF subversion and git services commented on ISIS-993: -- Commit 4f3932d3894aee180910d5bad24514fcc7bd3673 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=4f3932d ] ISIS-993: updating the components.xsd in docs directory > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178490#comment-15178490 ] ASF subversion and git services commented on ISIS-993: -- Commit 2c960ca9eb20756a92d6fe9f77b4c22dc507c267 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2c960ca ] ISIS-993: removing the ability to view the Grid as a view model (in its own right); no real use case for this functionality at the moment. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178491#comment-15178491 ] ASF subversion and git services commented on ISIS-993: -- Commit f763fce110a8bc40c49e5d38fd9b5f63aa4aaf0e in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f763fce ] ISIS-993: updating javadoc is all. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178485#comment-15178485 ] ASF subversion and git services commented on ISIS-993: -- Commit bf1288c28759b7f2b0bf0366f89eb4e7f13f9c1c in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bf1288c ] ISIS-993: minor refactoring of helper methos in GridNormalizerService implementations. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178487#comment-15178487 ] ASF subversion and git services commented on ISIS-993: -- Commit 7628fc9d309c8a58ca9f9bbe1e29fa5c5cc044e6 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7628fc9 ] ISIS-993: ensure columns in tables are rendered in correct order (require eagerly obtaining grid); also when rendering, ignore any invalid properties/collections/actions. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178486#comment-15178486 ] ASF subversion and git services commented on ISIS-993: -- Commit 2c62912527240861e2d26bbfac470f06dde70111 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2c62912 ] ISIS-993: only include entities and view models' layouts in zip file from MetadataMenu#downloadLayouts (XML) > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178488#comment-15178488 ] ASF subversion and git services commented on ISIS-993: -- Commit 393312e4a52a914bfd32d595925b22c700c37187 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=393312e ] ISIS-993: fixing unit test from refactoring of SpecificationCacheDefault earlier > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178492#comment-15178492 ] ASF subversion and git services commented on ISIS-993: -- Commit ff4d3427b501b37ee0a36ac3f69d67f39fa79526 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=ff4d342 ] ISIS-993: extending grid structure to include offsets and allow multiple col-XX-nn to be defined per column. Also tidied up the simpleapp: - removed .layout.json for HomePageViewModel, replaced with a .layout.xml - cleaned up SimpleObject (removing those test collections) - removed SimpleObject#updateName action. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178306#comment-15178306 ] ASF subversion and git services commented on ISIS-993: -- Commit f763fce110a8bc40c49e5d38fd9b5f63aa4aaf0e in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f763fce ] ISIS-993: updating javadoc is all. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178307#comment-15178307 ] ASF subversion and git services commented on ISIS-993: -- Commit ff4d3427b501b37ee0a36ac3f69d67f39fa79526 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=ff4d342 ] ISIS-993: extending grid structure to include offsets and allow multiple col-XX-nn to be defined per column. Also tidied up the simpleapp: - removed .layout.json for HomePageViewModel, replaced with a .layout.xml - cleaned up SimpleObject (removing those test collections) - removed SimpleObject#updateName action. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177758#comment-15177758 ] ASF subversion and git services commented on ISIS-993: -- Commit 2c960ca9eb20756a92d6fe9f77b4c22dc507c267 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2c960ca ] ISIS-993: removing the ability to view the Grid as a view model (in its own right); no real use case for this functionality at the moment. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177677#comment-15177677 ] ASF subversion and git services commented on ISIS-993: -- Commit 393312e4a52a914bfd32d595925b22c700c37187 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=393312e ] ISIS-993: fixing unit test from refactoring of SpecificationCacheDefault earlier > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177642#comment-15177642 ] ASF subversion and git services commented on ISIS-993: -- Commit 2c62912527240861e2d26bbfac470f06dde70111 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2c62912 ] ISIS-993: only include entities and view models' layouts in zip file from MetadataMenu#downloadLayouts (XML) > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177643#comment-15177643 ] ASF subversion and git services commented on ISIS-993: -- Commit 7628fc9d309c8a58ca9f9bbe1e29fa5c5cc044e6 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7628fc9 ] ISIS-993: ensure columns in tables are rendered in correct order (require eagerly obtaining grid); also when rendering, ignore any invalid properties/collections/actions. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173287#comment-15173287 ] ASF subversion and git services commented on ISIS-993: -- Commit e014bf80a823457bdbfc3acb5fac4b4a666715a1 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e014bf8 ] ISIS-993: when normalize, bind actions to properties or field sets (if metadata not already specified as an annotation). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173289#comment-15173289 ] ASF subversion and git services commented on ISIS-993: -- Commit bf1288c28759b7f2b0bf0366f89eb4e7f13f9c1c in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bf1288c ] ISIS-993: minor refactoring of helper methos in GridNormalizerService implementations. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173288#comment-15173288 ] ASF subversion and git services commented on ISIS-993: -- Commit e417a8ab5984393394113066a7ad1ea8379bcab2 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e417a8a ] ISIS-993: ensure that actions associated to properties/collections/fieldsets are added in the correct order when normalizing grid. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169140#comment-15169140 ] ASF subversion and git services commented on ISIS-993: -- Commit 62f69d173430efa00c0f06df84ba33aac1c188c1 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=62f69d1 ] Merge branch 'master' into ISIS-993 # Conflicts: # core/applib/src/main/java/org/apache/isis/applib/services/dto/Dto_downloadXml.java # core/applib/src/main/java/org/apache/isis/applib/services/jaxb/CatalogingSchemaOutputResolver.java > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169139#comment-15169139 ] ASF subversion and git services commented on ISIS-993: -- Commit df329882299524e194a7e9d0e86f497421eaa110 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=df32988 ] ISIS-993: minor changes, working towards being able to generate .layout.xml for complete vs normalized vs minimal (no longer NPEs for complete etc), however... ... not yet correctly roundtripping for anything other than the complete .layout.xml. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159870#comment-15159870 ] ASF subversion and git services commented on ISIS-993: -- Commit bf389208534eb8827892592a68659fd899f55437 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bf38920 ] ISIS-993: removing support for "isis.viewer.wicket.disableModalDialogs". Also: - adding stub release and migration notes for 1.12.0. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159877#comment-15159877 ] ASF subversion and git services commented on ISIS-993: -- Commit e4637ca801ef72c7861f4d0be1b69ad0c4fc5d6e in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e4637ca ] ISIS-993: yet more sorting out of positioning of actions in right drop-down. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159874#comment-15159874 ] ASF subversion and git services commented on ISIS-993: -- Commit 1841a12bb02fa30e6223eb65202c8dd2c9e07571 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1841a12 ] ISIS-993: honour namedEscaped for property edit prompt. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159876#comment-15159876 ] ASF subversion and git services commented on ISIS-993: -- Commit ce2ea3c5da907f886768e5a8a8554548322ebd3d in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=ce2ea3c ] ISIS-993: further fixes to honour namedEscaped for property edit prompt. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159878#comment-15159878 ] ASF subversion and git services commented on ISIS-993: -- Commit 34771c2416ba0f798a61595d18faa5dee7be9149 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=34771c2 ] ISIS-993: incidental, fix for Lombok with boolean properties (didn't find the @Property annotation). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159873#comment-15159873 ] ASF subversion and git services commented on ISIS-993: -- Commit 5c2b07de4bb30a490f4d3f12bab694e6fba161f5 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5c2b07d ] ISIS-993: responsibility for creating the default grid moved to GrdNormalizerService. Also Wicket viewer html layout fixes... that is: - tidying up of ScalarPanelAbstract html/layout, adding missing support for 'edit' button (and use fa-icon for that now, instead). - removing spurious concurrency exception resulting from new implementation of edit functionality (from action whose button is rendered on panel). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159872#comment-15159872 ] ASF subversion and git services commented on ISIS-993: -- Commit e95a46fcbb71d94de906b0a421ede677f96db964 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e95a46f ] ISIS-993: removing the fallback components also. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159871#comment-15159871 ] ASF subversion and git services commented on ISIS-993: -- Commit 6f435a16558099c12de5bb01af27af1b8a011a5f in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=6f435a1 ] ISIS-993: fixing bad import and javadoc. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159875#comment-15159875 ] ASF subversion and git services commented on ISIS-993: -- Commit 0f09648fa41b2af52af61d016842aa0102ab251c in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=0f09648 ] ISIS-993: more sorting out of positioning of actions in right drop-down. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149602#comment-15149602 ] ASF subversion and git services commented on ISIS-993: -- Commit e57acf256b1c727475be62fed70e1d6a07f28327 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e57acf2 ] ISIS-993: starting to remove the FC (fixed col) stuff ... moving out FCColumn.Hint enum. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149603#comment-15149603 ] ASF subversion and git services commented on ISIS-993: -- Commit de3e385f02d1941a569934bdfc583c3839488b08 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=de3e385 ] ISIS-993: first-cut of single-edit properties (using modal prompt dialog). Prereq for removing the FixedCol stuff. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149601#comment-15149601 ] ASF subversion and git services commented on ISIS-993: -- Commit a40a8696f3fde8e02d82d3bf409052b898d2dc5e in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a40a869 ] ISIS-993: reuse Wicket's isVisible() for dynamically visible content (refactor of HasDynamicallyVisibleContent interface). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147345#comment-15147345 ] ASF subversion and git services commented on ISIS-993: -- Commit 30bfe8c62bbf2fa3894ccc52afb7719cf66f4bca in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=30bfe8c ] ISIS-993: improving derivation of properties when layout xml exists with field sets and actions bound to those fieldsets only through @MemberOrder#name annotation. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147346#comment-15147346 ] ASF subversion and git services commented on ISIS-993: -- Commit f65487e46008680f6368afc186e5f43513dfc50b in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f65487e4 ] ISIS-993: dynamically evaluate visibility of tabpanel, tab, row, col, fieldset and collection (suppress parent containers if there would be nothing to show). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147074#comment-15147074 ] ASF subversion and git services commented on ISIS-993: -- Commit 697bcdbc59341a10f4bb6f645bb3c856ab6226fc in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=697bcdb ] ISIS-993: better derivation of default grid from existing metadata when none is available. Also: - allow actions to be associated in @MemberOrder#name with fieldset ids; wire up to first property within that fieldset - associate the (framework-provided downloadLayoutXml and downloadJdoMetadata actions with "metadata" fieldset. - some fixes for CSS for dropdowns > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147073#comment-15147073 ] ASF subversion and git services commented on ISIS-993: -- Commit 2bde2a1e50b025d1a052829b99376da77a8a66b2 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2bde2a1 ] ISIS-993: suppress properties from fieldsets that should be invisible. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144342#comment-15144342 ] ASF subversion and git services commented on ISIS-993: -- Commit bbd593bc10ab486aad16cc7eff6dd3b2e06a0222 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bbd593b ] ISIS-993: guard against invisible actions corresponding to null links. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144343#comment-15144343 ] ASF subversion and git services commented on ISIS-993: -- Commit d2340ebd5839d94b0976f00a530e4daba6c41b45 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d2340eb ] ISIS-993: associate properties into their correct fieldsets, honouring ordering. Also order collections. in addition: - bug fix to suppress not contributed collections (from superclasses) being rendered also as actions - tweak to CSS for BS3 layout - move DeweyComparator to metamodel module (from runtime module). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141746#comment-15141746 ] ASF subversion and git services commented on ISIS-993: -- Commit 959d42477b4aefa383c562f166a91be630e3f3eb in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=959d424 ] ISIS-993: GridFacetDefault now derives a grid from facets if no XML is available. This design probably means that a lot of the existing "fixedcol" code could be removed; in effect we always render using BS3. Will leave in for the moment, though. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141745#comment-15141745 ] ASF subversion and git services commented on ISIS-993: -- Commit 41040399c22304b128f738871dfade1b1eda49c1 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=4104039 ] Merge branch 'master' into ISIS-993 > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140664#comment-15140664 ] ASF subversion and git services commented on ISIS-993: -- Commit ecf6d1708be0a409cd8fb5d0257235b3b0de1f5b in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=ecf6d17 ] ISIS-993: hold the domainClass within the grid. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140662#comment-15140662 ] ASF subversion and git services commented on ISIS-993: -- Commit 5c831757d34919ab7b36f84a6e6579a4061a97e3 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5c83175 ] ISIS-993: introducing the concept of minimal/normalized/complete grids (still WIP) Also: - moved responsibility for determining the available set of gridNormalizerServices to GridService (ensure only one such per grid implementation) - moved the FC applib classes into the metamodel, so no longer public API. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140665#comment-15140665 ] ASF subversion and git services commented on ISIS-993: -- Commit 78943221cc6eccc0afed292910bb84a62b8a37bf in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7894322 ] ISIS-993: can now download normalized, complete or minimal layouts. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140663#comment-15140663 ] ASF subversion and git services commented on ISIS-993: -- Commit 6053d1a8efed2d5cae9cbbc8b0497796397686cd in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=6053d1a ] ISIS-993: fleshing out the GridNormalizerServiceAbstract for the "complete" and "minimal" updating of Grid graphs (prior to conversion to XML). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138013#comment-15138013 ] ASF subversion and git services commented on ISIS-993: -- Commit 082916aeb4dcf34949789b0fa01caf47b27437b9 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=082916a ] ISIS-993: changed the suppression algorithm: now, will render any tab group with only a single tab as that tab's rows. This allows tab groups to alternate with field sets etc. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138014#comment-15138014 ] ASF subversion and git services commented on ISIS-993: -- Commit f3e8bbfc052a060e80ae350999b787438b0d4168 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f3e8bbf ] ISIS-993: improving the suppression algorithm, now search for any content under a tab (however deep), if none found then suppress the tab (which may in turn mean suppressing the tab group and just rendering the rows of the first tab). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138012#comment-15138012 ] ASF subversion and git services commented on ISIS-993: -- Commit 2ae2df1ba64bedad1ce9bf228335194e3bffb258 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2ae2df1 ] ISIS-993: if column contains only a single tabgroup and that tabgroup contains only a single tab, then just render the rows within that tab. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134034#comment-15134034 ] ASF subversion and git services commented on ISIS-993: -- Commit f233f418a340c319648f756436265c7368bd3697 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=f233f41 ] ISIS-993: deleting unused fields from CollectionContentsMultipleViewsPanel > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131890#comment-15131890 ] ASF subversion and git services commented on ISIS-993: -- Commit 20faf33a050b10e0085b01cc027d6d0ef6dd4386 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=20faf33 ] ISIS-993: Now allow unreferenced collections to be associated with columns. Also sorting out hints for collection selection under tabs. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131159#comment-15131159 ] ASF subversion and git services commented on ISIS-993: -- Commit 8fcac96481cb21a47d8db0a64a76fa4693d5582d in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8fcac96 ] ISIS-993: unreferenced properties/actions/collectoins handling > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131158#comment-15131158 ] ASF subversion and git services commented on ISIS-993: -- Commit fe46a781eb7472694e705cfd396e630964c3add3 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=fe46a78 ] ISIS-993: normalizing the BS3 grid, factoring out commonalities into superclass. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127338#comment-15127338 ] ASF subversion and git services commented on ISIS-993: -- Commit c57d8cd8ed656813ae9f17da68f9098450633b74 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=c57d8cd ] ISIS-993: bootstrap3 layout working, more or less. Still need to do the normalization phase. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127336#comment-15127336 ] ASF subversion and git services commented on ISIS-993: -- Commit d7a1ee2ddae809ef630d48d32953ae6ae736eedf in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d7a1ee2 ] ISIS-993: working towards storing a single hint on the EntityModel > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127341#comment-15127341 ] ASF subversion and git services commented on ISIS-993: -- Commit 63d03d29b1929b481f72eed943ca22eacb2124f8 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=63d03d2 ] ISIS-993: converting GridNormalizer into a service. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127335#comment-15127335 ] ASF subversion and git services commented on ISIS-993: -- Commit fc59d351325454489fe22382b8c41ac4ae30f1e5 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=fc59d35 ] ISIS-993: store hint on the column, rather than pass around separately. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127339#comment-15127339 ] ASF subversion and git services commented on ISIS-993: -- Commit 25a267a61cf6d4c9ef297f19f134e25dd17e7a91 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=25a267a ] ISIS-993: starting on the visitor/normalization stuff for BS3 grid. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127340#comment-15127340 ] ASF subversion and git services commented on ISIS-993: -- Commit 7fb6355663b4ccddba24e7ebe47774f56b62c148 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7fb6355 ] ISIS-993: renamed Page to Grid, PageFacet to GridFacet, PageService to GridService, PageNormalizerService to GridNormalizerService, BS3PagePanel to BS3GridPanel, FCPagePanel to FCGridPanel, Also regenerated bootstrap3.xsd for new id attrs and sorted out an issue with the unreferencedXxx attrs so that they can be optional. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127337#comment-15127337 ] ASF subversion and git services commented on ISIS-993: -- Commit 84c9cf7585ddb4d8870c423643025bc29ca1df63 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=84c9cf7 ] ISIS-993: use a single layoutMetadata hint in EntityModel, rather than many different hints. Also, moved FC classes under a new "fixedcols" layout. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125293#comment-15125293 ] ASF subversion and git services commented on ISIS-993: -- Commit 10d80f3a850ad602d775b09098405b3b56c2541a in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=10d80f3 ] ISIS-993: still sketching out the layout classes for BS3 and FC (fixed col) > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125294#comment-15125294 ] ASF subversion and git services commented on ISIS-993: -- Commit 8f0abcdb64e98ab5e6d3aa30fd32f62444891a62 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8f0abcd ] ISIS-993: introduction of the PageNormalizerService as an internal SPI which keeps track of the different Page implementations and their algorithms for normalizing themselves. The original FixedCol layout is now working again as of this commit. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125295#comment-15125295 ] ASF subversion and git services commented on ISIS-993: -- Commit 65f7d320fa95cf45aa6db99f66e1165b2ba4f5d8 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=65f7d32 ] ISIS-993: bootstrap3 schema now properly defined and serializing ok. Also juggling around with the common (nee members) > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125292#comment-15125292 ] ASF subversion and git services commented on ISIS-993: -- Commit 517b6ccbb3e523f084f739fd73d009a86cc7c6c5 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=517b6cc ] ISIS-993: working towards a 'bootstrap3' layout > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125291#comment-15125291 ] ASF subversion and git services commented on ISIS-993: -- Commit b72bce9050b3bc34c32b8a1902fbb7be7789de23 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b72bce9 ] Merge branch 'master' into ISIS-993 > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117123#comment-15117123 ] ASF subversion and git services commented on ISIS-993: -- Commit 0cefc70732995d60e3be242eacb1597a3e2ebf1e in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=0cefc70 ] ISIS-993: ScopedSessionAttribute now using Component rather than HasPath. That means that the state of the page (selected tabs, selected collection view) is being persisted and honoured in the session correctly. Also added in new implementations of UiHintPathSignificant, however this bit is incomplete... hacked the fullHintPathFor(...) to ignore the fact as to whether a component is "UI Hint path significant" or not. Intention in next commit is to simplify and get rid of this interface, just use all the components in the page as being significant. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117126#comment-15117126 ] ASF subversion and git services commented on ISIS-993: -- Commit efe98ca6efbfea7d55930a3676b1b10e82805cb2 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=efe98ca ] ISIS-993: removing one final remnant of UiHintPathSignficant. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117124#comment-15117124 ] ASF subversion and git services commented on ISIS-993: -- Commit b8576fce76150fbcc3a179fc3935041c22b665e9 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b8576fc ] ISIS-993: getting rid of UiHintSignificantComponent > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117121#comment-15117121 ] ASF subversion and git services commented on ISIS-993: -- Commit c05bde0f5e9358db24ee9124243ef7856bfdc1b7 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=c05bde0 ] ISIS-993: create the EntityCollectionModel from the EntityModel with CollectionLayoutMetadata, rather than passing the OTMA around. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117127#comment-15117127 ] ASF subversion and git services commented on ISIS-993: -- Commit 74e5bd0c5ab3bdc4256b748da067414dd3b6be48 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=74e5bd0 ] ISIS-993: getting rid of HintUtil class, moving into UiHintContainer.Util > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117122#comment-15117122 ] ASF subversion and git services commented on ISIS-993: -- Commit bdbd5036fcd5823efaaad645923b92b2a6628c8d in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bdbd503 ] ISIS-993: factored out EntityCollectionPanel from EntityCollectionsPanel. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117125#comment-15117125 ] ASF subversion and git services commented on ISIS-993: -- Commit 8b49e1c48311a1195f653b9f09f446b23a41f35c in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8b49e1c ] ISIS-993: getting rid of the HasPath interface. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115346#comment-15115346 ] ASF subversion and git services commented on ISIS-993: -- Commit 35201392b424e507e6fc54d6fe8e7381e37b04c8 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3520139 ] ISIS-993: SessionScopedAttribute factored out, now used for the selectedItem drop-down so that the system remembers which view to use for rendering a collection (for a particular object). > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115350#comment-15115350 ] ASF subversion and git services commented on ISIS-993: -- Commit 1f764b506970528862c5cf81209335674d53ea62 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1f764b5 ] ISIS-993: factored out PropertyGroup component. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115349#comment-15115349 ] ASF subversion and git services commented on ISIS-993: -- Commit 205cf8539457f8294daa723301e75b615ca0de89 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=205cf85 ] ISIS-993: working towards factoring out a PropertyGroup component. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115345#comment-15115345 ] ASF subversion and git services commented on ISIS-993: -- Commit d946027a36293d3e800c393f01aa145b8bc23b20 in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d946027 ] ISIS-993: renaming of components, EntityCombinedPanel now called EntityEditablePanel. Other subsidiary panels moved alongside. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115343#comment-15115343 ] ASF subversion and git services commented on ISIS-993: -- Commit fc5355f5dad5b81e67d0e3f1121b5e88ecf4e3fe in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=fc5355f ] ISIS-993: in process of converting TabbedPanel into own panel. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115347#comment-15115347 ] ASF subversion and git services commented on ISIS-993: -- Commit 376ab6f06d716005d9073a6022c82730e3401c9b in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=376ab6f ] ISIS-993: can now store multiple different session attributes on an EntityCollectionModel. > 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)
[jira] [Commented] (ISIS-993) Show different object members on multiple tabs
[ https://issues.apache.org/jira/browse/ISIS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115348#comment-15115348 ] ASF subversion and git services commented on ISIS-993: -- Commit cddf25c3af8e41fc758f1b22b618d143cb4f in isis's branch refs/heads/ISIS-993 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=cddf255 ] ISIS-993: attempting to unify the existing UiHintContainer and the ScopedSessionAttribute stuff; only part way there. > 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)
