[ https://issues.apache.org/jira/browse/ISIS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723924#comment-13723924 ]
ASF subversion and git services commented on ISIS-468: ------------------------------------------------------ Commit fba0a7186024c261c3fa27e94cad580d0048e5ec in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=fba0a71 ] ISIS-468: fix for 3-column properties... ... right-hand side had incorrect span > Provide better layout management of pages in the Wicket viewer. > --------------------------------------------------------------- > > Key: ISIS-468 > URL: https://issues.apache.org/jira/browse/ISIS-468 > Project: Isis > Issue Type: New Feature > Components: Core, Viewer: Wicket > Affects Versions: viewer-wicket-1.2.0, core-1.2.0 > Reporter: Dan Haywood > Assignee: Dan Haywood > Priority: Minor > Fix For: viewer-wicket-1.3.0, core-1.3.0 > > > In the Wicket viewer, it can be difficult to distinguish different types of > entities, moreover for some entities (with more properties than collections) > there is a lot of real-estate wasted. > This ticket is to provide the ability for laying the properties out over up > to three columns, and optionally suppressing the collections column. > Moreover it should be able to specify the relative width of those columns, > and, ideally, the website should be responsive. > ~~~ > In the applib, introduce a new @MemberGroupLayout annotation, replacing the > current @MemberGroups annotation, allowing this information to be specified, > eg: > @MemberGroupLayout( > columnSpans={3,3,0,6}, > left={"General", "Dates"} > middle={"Notes"} > } > would place the properties in two columns taking up half the page, and > collections (fourth column) to the far right. taking up the remaining 50%. > eg: > @MemberGroupLayout( > columnSpans={4,4,4,0}, > left={"General", "Dates"} > middle={"Notes"}, > right={"Other"} > } > would suppress the collections. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira