[
https://issues.apache.org/jira/browse/ISIS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829883#comment-13829883
]
ASF subversion and git services commented on ISIS-600:
------------------------------------------------------
Commit 6084ae6d0f072fe2134220dbab7ab02dfeaf59ac in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=6084ae6 ]
ISIS-600, ISIS-601: paged facet in layout JSON
along with internal refactoring of format of properties file.
> Change format of facet properties file, scope by member then facet
> ------------------------------------------------------------------
>
> Key: ISIS-600
> URL: https://issues.apache.org/jira/browse/ISIS-600
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.3.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: core-1.4.0
>
>
> Although layout facets are most likely to be represented in json, they can
> also be loaded from a properties file. Internally the json is converted to a
> bunch of properties, and it is the properties that are parsed and used to
> create facets.
> Since this stuff was originally done for the memberOrder and
> memberOrderLayout facets, the properties file syntax is currently:
> memberOrder.<memberName>.name=
> memberOrder.<memberName>.sequence=
> and
> memberOrderLayout.columnSpans=3,4,0,5
> memberOrderLayout.columnSpans.left=General,Detail
> etc
> This ticket is to invert this ordering, in preparation for other facets being
> added, and to distinguish member-level facets from class-level facets.
> eg:
> member.<memberName>.memberOrder.name=
> member.<memberName>.memberOrder.sequence=
> and
> memberOrderLayout.columnSpans=3,4,0,5
> memberOrderLayout.columnSpans.left=General,Detail
> The format of the JSON file is unchanged.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
