You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2012/12/17 00:10:14 UTC

[jira] [Updated] (ISIS-263) Introduce a new @CommonlyUsed annotation as a hint for the UI. To be implemented by Wicket viewer (as a minimum)

     [ https://issues.apache.org/jira/browse/ISIS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-263:
-----------------------------

    Fix Version/s: isis-viewer-wicket-1.0.0
    
> Introduce a new @CommonlyUsed annotation as a hint for the UI.  To be implemented by Wicket viewer (as a minimum)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-263
>                 URL: https://issues.apache.org/jira/browse/ISIS-263
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core, Viewer: Wicket
>    Affects Versions: 0.2.0-incubating
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: isis-1.0.0, isis-viewer-wicket-1.0.0
>
>
> The @CommonlyUsed annotation iIndicates that a class member is commonly used and so should
>  be presented in the viewer in an appropriate manner.
> For example, an Order#lineItems collection might be "opened" automatically so that the user could see a list of line items immediately when the order is rendered.
> Or, a property containing an <tt>Address</tt> might show the referenced address as an embeddded property.
> Or, an action <tt>Submit</tt> might be rendered as a button rather than buried inside a submenu somewhere.
> For properties and collections there is some similarity between this concept and that of eager-loading as supported by some object stores.  Indeed, some object stores may choose use their own specific annotations (eg a JDO default fetch group) in order to infer this semantic.

--
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