[ 
https://issues.apache.org/jira/browse/ISIS-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543658#comment-14543658
 ] 

Dan Haywood edited comment on ISIS-1151 at 5/14/15 1:23 PM:
------------------------------------------------------------

agreed, this should live in @CollectionLayout.

One issue is that this cannot be type-safe; we can't enumerate all possible 
views in an enum, for example, because there could be new views (addons) in the 
future.  So I think it'll just need to be a simple string.  Each view/addon 
should clearly document its id, eg "fullcalendar2" or "gmap3".

{code}
@CollectionLayout(
    defaultView="fullcalendar2"
)
public SortedSet<ToDoItem> getDependencies()
{code}

or 

{code}
"collections": {
    "dependencies": {
        "collectionLayout": {
            "defaultView": "fullcalendar2"
         }
     }
}
{code}




was (Author: danhaywood):
agreed, this should live in @CollectionLayout.

One issue is that this cannot be type-safe; we can't enumerate all possible 
views in an enum, for example, because there could be new views (addons) in the 
future.  So I think it'll just need to be a simple string.  Each view/addon 
should clearly document its id, eg "fullcalendar2" or "gmap3".

@CollectionLayout(
    defaultView="fullcalendar2"
)
public SortedSet<ToDoItem> getDependencies()

or 

"collections": {
    "dependencies": {
        "collectionLayout": {
            "defaultView": "fullcalendar2"
         }
     }
}



> Allow the default view of a collection to be set
> ------------------------------------------------
>
>                 Key: ISIS-1151
>                 URL: https://issues.apache.org/jira/browse/ISIS-1151
>             Project: Isis
>          Issue Type: Improvement
>            Reporter: Sander Ginn
>            Assignee: Dan Haywood
>
> Currently a collection defaults to the table view. I'd like to be able to set 
> a different view (e.g. the calendar) to default. Perhaps via 
> @CollectionLayout? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to