[
https://issues.apache.org/jira/browse/ISIS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693236#comment-16693236
]
Andi Huber commented on ISIS-1999:
----------------------------------
We do have the 'o.a.i.applib.annotation.***Layout#describedAs', which sadly
holds a constant string, that has to be specified at compile-time.
Would it be feasible to change or extend 'describedAs' to allow for more
advanced use-cases?
Eg. describedAs could be of type Class<X> where X is some interface that suites
well, such that we can generate 'describedAs' content on the fly and also on
the fly decide whether to display as tooltip or some more advanced (help) page.
> 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
>
>
> 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).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
