You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/09/27 14:14:03 UTC
[jira] [Commented] (ISIS-469) Provide implementations of certain
layout facets that read from a "Xxx.layout.properties" file
[ https://issues.apache.org/jira/browse/ISIS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779859#comment-13779859 ]
ASF subversion and git services commented on ISIS-469:
------------------------------------------------------
Commit 6f2a5cd2ef4c501acb2f618e2dc9f641036e87ba in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=6f2a5cd ]
ISIS-469, 475: change to example app's pom to ensure that ..
.. the .layout.json files are included in the lib when built as a war
> Provide implementations of certain layout facets that read from a "Xxx.layout.properties" file
> ----------------------------------------------------------------------------------------------
>
> Key: ISIS-469
> URL: https://issues.apache.org/jira/browse/ISIS-469
> Project: Isis
> Issue Type: New Feature
> Components: Core
> Affects Versions: core-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: core-1.3.0
>
>
> Specifically, the two layout facets to capture are MemberOrderFacet and MemberGroupLayoutFacet (see ISIS-468).
> The idea of this ticket is that information is pulled in from a separate file, sitting alongside the domain class. This makes it easier to see this layout information in one place.
> And, in conjunction with ISIS-470, this would allow dynamic updates to the layout, without a recompile/redeploy.
> This ticket defines the metadata informatino in an Xxx.layout.properties file. (Note that ISIS-475 takes this idea further and specifies a JSON file. This latter idea is probably to be preferred in most cases).
> The format of the property file (Xxx.layout.properties) is:
> ###########################################
> # MemberGroupLayout
> ###########################################
> memberGroupLayout.columnSpans=3,4,0,5
> memberGroupLayout.left=General
> memberGroupLayout.middle=Detail
> memberGroupLayout.right=
> ###########################################
> # MemberOrder
> ###########################################
> # Properties
> memberOrder.description.sequence=1
> memberOrder.category.sequence=2
> memberOrder.complete.sequence=3
> # Properties (Detail)
> memberOrder.dueBy.name=Detail
> memberOrder.cost.name=Detail
> memberOrder.notes.name=Detail
> memberOrder.attachment.name=Detail
> memberOrder.dueBy.sequence=1
> memberOrder.cost.sequence=2
> memberOrder.notes.sequence=3
> memberOrder.attachment.sequence=4
> # Properties (Misc)
> memberOrder.versionSequence.name=Misc
> memberOrder.versionSequence.sequence=99
> #Collections
> memberOrder.dependencies.sequence=1
> memberOrder.similarItems.sequence=2
> #Actions (freestanding)
> memberOrder.delete.sequence=1
> memberOrder.duplicate.sequence=2
> #Actions (associated with properties)
> memberOrder.completed.name=complete
> memberOrder.notYetCompleted.name=complete
> memberOrder.completed.sequence=1
> memberOrder.notYetCompleted.sequence=2
> memberOrder.updateCost.name=cost
> #Actions (associated with collections)
> memberOrder.add.name=dependencies
> memberOrder.remove.name=dependencies
--
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