Nice feature! I have two suggestions: @CommonlyUsed doesn't describe the
the desired result of the annotation. I would prefer something like
@Expanded with a parameter for true or false. And as I like system defaults
I propose a property to store it: isis.viewers.expanded.collections=true

But feel free to ignore ;-)

Cheers,

Jeroen

-- 
Jeroen van der Wal
Stromboli b.v.
+31 655 874050


On Wed, Sep 5, 2012 at 8:32 PM, Dan Haywood (JIRA) <[email protected]> wrote:

>
>      [
> https://issues.apache.org/jira/browse/ISIS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Dan Haywood resolved ISIS-263.
> ------------------------------
>
>     Resolution: Fixed
>
> > 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: MetaModel, Core: ProgModel, Viewer: Wicket
> >    Affects Versions: 0.2.0-incubating
> >            Reporter: Dan Haywood
> >            Assignee: Dan Haywood
> >            Priority: Minor
> >             Fix For: 0.3.1-incubating
> >
> >
> > 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
>

Reply via email to