[
https://issues.apache.org/jira/browse/ISIS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-975:
-----------------------------
Description:
Currently we have the ability to make actions into a prototype, meaning that
they are only shown in prototype mode (--type SERVER_PROTOTYPE or Wicket
development mode) and hidden during production mode (--type SERVER, or Wicket
deployment mode).
Because of they way that they are implemented, contributed properties and
contributed collections also "inherit" this prototyped-ness; they will also be
hidden in prototype mode.
However, there is no way to hide regular (non-contributed) properties or
collections when not running in prototype mode.
~~~
Don't think that this is a particularly significant issue, but it is an area of
asymmetry in our metamodel so should probably be cleaned up, ie by introducing
the notion of prototype for properties or collections.
This should be implemented as a new "prototype" attribute in @PropertyLayout
and @CollectionLayout.
The Wicket viewer will need to honour this when rendering the entity forms
(EntityPropertiesForm component etc).
was:
ie as per http://fortawesome.github.io/Font-Awesome/examples/#bootstrap
using:
@PropertyLayout(
cssClassFa="fa fa-fw fa-envelope-o"
)
public String getEmailAddress() { ... }
etc.
> Allow the prototype facet to be associated with properties and collections,
> not just actions.
> ---------------------------------------------------------------------------------------------
>
> Key: ISIS-975
> URL: https://issues.apache.org/jira/browse/ISIS-975
> Project: Isis
> Issue Type: Improvement
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: viewer-wicket-1.9.0, core-1.9.0
>
>
> Currently we have the ability to make actions into a prototype, meaning that
> they are only shown in prototype mode (--type SERVER_PROTOTYPE or Wicket
> development mode) and hidden during production mode (--type SERVER, or Wicket
> deployment mode).
> Because of they way that they are implemented, contributed properties and
> contributed collections also "inherit" this prototyped-ness; they will also
> be hidden in prototype mode.
> However, there is no way to hide regular (non-contributed) properties or
> collections when not running in prototype mode.
> ~~~
> Don't think that this is a particularly significant issue, but it is an area
> of asymmetry in our metamodel so should probably be cleaned up, ie by
> introducing the notion of prototype for properties or collections.
> This should be implemented as a new "prototype" attribute in @PropertyLayout
> and @CollectionLayout.
> The Wicket viewer will need to honour this when rendering the entity forms
> (EntityPropertiesForm component etc).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
