[
https://issues.apache.org/jira/browse/ISIS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716890#comment-16716890
]
Dan Haywood commented on ISIS-1999:
-----------------------------------
I also like the idea. It wouldn't be a change, this is instead about the
implementation of the DescribedAsFacet. I see it being implemented similar to
MustSatisfyFacet which instantiates a specification in order to potentially
invalidate.
We could therefore have:
{code}
@PropertyLayout(describedWith=FirstNameDescriber.class)
private String firstName;
{code}
where:
{code}
public static class FirstNameDescribed implements Describer {
String description(Object domainObject, String memberId);
}
{code}
probably with an optional Describer2 for i18n:
{code}
public static class FirstNameDescriber2 implements Describer2 {
TranslatableString description(Object domainObject, String memberId);
}
{code}
> For action mixins, allow read-only properties and collections to be defined,
> to show useful/relevant context data.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-1999
> URL: https://issues.apache.org/jira/browse/ISIS-1999
> Project: Isis
> Issue Type: New Feature
> Affects Versions: 1.16.2
> Reporter: Dan Haywood
> Priority: Major
> Fix For: 1.16.3
>
> Attachments: sketch.pptx
>
>
> These would simply be rendered underneath the OK/Cancel button.
> One property might also show help markup, or hyperlink to reference guides
> etc.
> As a refinement (perhaps split out to separate story), allow a layout file
> (with same name( as mixin to be specified. Perhaps this might even (through
> some extension to the existing syntax) allow the parameters to be laid out
> differently, eg over multiple columns).
> ~~~
> * https://bootstrapious.com/p/bootstrap-sidebar
> * https://bootsnipp.com/tags/sidebar
> *
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
