You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2015/03/17 14:19:38 UTC

[jira] [Comment Edited] (ISIS-1098) Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API)

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

Martin Grigorov edited comment on ISIS-1098 at 3/17/15 1:19 PM:
----------------------------------------------------------------

I think the ***Layout annotations should be extended.
Or even introduce a special annotation for temporal properties/parameters ?! Because the JS widget has many settings: http://eonasdan.github.io/bootstrap-datetimepicker/Options/. 

For ISIS-1095 I needed just: http://eonasdan.github.io/bootstrap-datetimepicker/Options/#viewmode
You can see it in action at http://eonasdan.github.io/bootstrap-datetimepicker/#view-mode. With "years" viewMode the picker asks you first to select the year, then the month and finally the date. This is much easier for selecting a birthdate than trying to navigate with the default view (http://eonasdan.github.io/bootstrap-datetimepicker/#minimum-setup)


was (Author: mgrigorov):
I think the ***Layout annotations should be extended.
Or even introduce a special annotation for temporal properties/parameters ?! Because the JS widget has many settings: http://eonasdan.github.io/bootstrap-datetimepicker/Options/. 

For ISIS-1095 I needed just: http://eonasdan.github.io/bootstrap-datetimepicker/Options/#viewmode
You can see it in action at http://eonasdan.github.io/bootstrap-datetimepicker/#view-mode. With "years" viewMode the picker asks you first to select the year, then the month and finally the date. This is much easier to selecting a birthdate than trying to navigate with the default view (http://eonasdan.github.io/bootstrap-datetimepicker/#minimum-setup)

> Extend @Property and @Parameter facets to provide additional hints (ie make ISIS-1095 into formal API)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-1098
>                 URL: https://issues.apache.org/jira/browse/ISIS-1098
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: core-1.8.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 1.10.0
>
>
> see https://issues.apache.org/jira/browse/ISIS-1095 for background.
> arguably it should be @PropertyLayout and @ParameterLayout annotations that we extend, rather than @Property and @Parameter
> ... depends on how "intrinsic" to the domain this hint is.
> Opinions?



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