You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/02/01 09:08:00 UTC
[jira] [Commented] (ISIS-2877) Support for Value Type Composition
[ https://issues.apache.org/jira/browse/ISIS-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485132#comment-17485132 ]
ASF subversion and git services commented on ISIS-2877:
-------------------------------------------------------
Commit 5e68ed3efc6caa6783f367aee834d86d64910a97 in isis's branch refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=5e68ed3 ]
ISIS-2877: fixes xml based value-types
- also activating test scenarios
> Support for Value Type Composition
> ----------------------------------
>
> Key: ISIS-2877
> URL: https://issues.apache.org/jira/browse/ISIS-2877
> Project: Isis
> Issue Type: Improvement
> Components: Isis Core, Isis Viewer Wicket
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-RC1
>
>
> It should be sufficient to specify a value-type say CalendarEvent to be a compound of already existing value-types (date, time, duration, title, notes) = base-types, without the need of further integration with the UI.
> Given all the required information via a ValueSemanticsProvider, the framework should be smart enough to handle:
> * property update dialogs (optional - for that to work, we might just require an update action that takes all required base-types as arguments)
> * action dialogs (eg. just embed the base-types)
> * table columns (eg. just embed the base-types, or as an alternative use value semantics 'rendering')
--
This message was sent by Atlassian Jira
(v8.20.1#820001)