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 2011/01/17 12:51:45 UTC
[jira] Created: (ISIS-74) Get rid of BoundedFacet (or keep only for
information); instead replace with ChoicesFacetBecauseBounded.
Get rid of BoundedFacet (or keep only for information); instead replace with ChoicesFacetBecauseBounded.
--------------------------------------------------------------------------------------------------------
Key: ISIS-74
URL: https://issues.apache.org/jira/browse/ISIS-74
Project: Isis
Issue Type: Improvement
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
Fix For: 0.1.0-incubating
Currently if a type is annotated as @Bounded, then we install a BoundedFacet and the viewers are expected to render a drop-down list. It would be more straightforward to simply have @Bounded imply a ChoicesFacet, and therefore get rid of this special-case processing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (ISIS-74) Get rid of BoundedFacet (or keep only
for information); instead replace with ChoicesFacetBecauseBounded.
Posted by "Dan Haywood (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-74:
----------------------------
Component/s: Core: MetaModel
> Get rid of BoundedFacet (or keep only for information); instead replace with ChoicesFacetBecauseBounded.
> --------------------------------------------------------------------------------------------------------
>
> Key: ISIS-74
> URL: https://issues.apache.org/jira/browse/ISIS-74
> Project: Isis
> Issue Type: Improvement
> Components: Core: MetaModel
> Reporter: Dan Haywood
> Priority: Minor
>
> Currently if a type is annotated as @Bounded, then we install a BoundedFacet and the viewers are expected to render a drop-down list. It would be more straightforward to simply have @Bounded imply a ChoicesFacet, and therefore get rid of this special-case processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ISIS-74) Get rid of BoundedFacet (or keep only for
information); instead replace with ChoicesFacetBecauseBounded.
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-74:
----------------------------
Fix Version/s: (was: 0.1.0-incubating)
Assignee: (was: Dan Haywood)
> Get rid of BoundedFacet (or keep only for information); instead replace with ChoicesFacetBecauseBounded.
> --------------------------------------------------------------------------------------------------------
>
> Key: ISIS-74
> URL: https://issues.apache.org/jira/browse/ISIS-74
> Project: Isis
> Issue Type: Improvement
> Reporter: Dan Haywood
> Priority: Minor
>
> Currently if a type is annotated as @Bounded, then we install a BoundedFacet and the viewers are expected to render a drop-down list. It would be more straightforward to simply have @Bounded imply a ChoicesFacet, and therefore get rid of this special-case processing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.