[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=17527433#comment-17527433 ] ASF subversion and git services commented on ISIS-2877: --- Commit cac084fd2c57d4ee8e82b97c7508b6313ca96c1b in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=cac084fd2c ] ISIS-2877: css fix: remove potentially superfluous paading overrides - also center boolean panels within table cells > 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.7#820007)
[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=17527421#comment-17527421 ] ASF subversion and git services commented on ISIS-2877: --- Commit 081cfe5e1be9c96e8a9b2969da4a1943afde10f3 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=081cfe5e1b ] ISIS-2877: css fix: consistent link coloring > 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.7#820007)
[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=17527414#comment-17527414 ] ASF subversion and git services commented on ISIS-2877: --- Commit 461f878c0931b6771123fb60046f350db8b932a2 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=461f878c09 ] ISIS-2877: css fix: contrast fix for badges inside tables (flatly) > 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.7#820007)
[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=17527392#comment-17527392 ] ASF subversion and git services commented on ISIS-2877: --- Commit 962ba54441076680addcb347726a9f3aedd13056 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=962ba54441 ] ISIS-2877: js fix: focus on checkbox when entering boolean scalar value edit > 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.7#820007)
[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=17527389#comment-17527389 ] ASF subversion and git services commented on ISIS-2877: --- Commit 3862de5b0732e6c1d0c942b9fd104b6050569671 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=3862de5b07 ] ISIS-2877: css fix: fit button-group inside surrounding value input box > 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.7#820007)
[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=17520585#comment-17520585 ] ASF subversion and git services commented on ISIS-2877: --- Commit ada56900573999bb735846e3cdd895ac2939 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ada569005e ] ISIS-2877: popover clearing fixes > 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)
[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=17520581#comment-17520581 ] ASF subversion and git services commented on ISIS-2877: --- Commit fd635a12ed2182114ce36a881c3e899492004904 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=fd635a12ed ] ISIS-2877: remove dead code > 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)
[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=17520586#comment-17520586 ] ASF subversion and git services commented on ISIS-2877: --- Commit da66bae58e6e30aa8e0cabc982c33711ae58772b in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=da66bae58e ] ISIS-2877: Workaround BootstrapFileInputField not reacting to clearing of underlying model. > 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)
[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=17520580#comment-17520580 ] ASF subversion and git services commented on ISIS-2877: --- Commit 42609533d666b4a8aa6563ec064e0aa1de8f7d20 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=42609533d6 ] ISIS-2877: route clear field click through form-executor > 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)
[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=17520575#comment-17520575 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5d0ffb95446170d263368d89bea845553bfb2244 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5d0ffb9544 ] ISIS-2877: purge the legacy edit button > 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)
[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=17520578#comment-17520578 ] ASF subversion and git services commented on ISIS-2877: --- Commit 99e354208a349dabdcb3bcc9386855c65a5a4361 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=99e354208a ] ISIS-2877: adds support for additional buttons - when hovering over the edit prompt link > 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)
[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=17520583#comment-17520583 ] ASF subversion and git services commented on ISIS-2877: --- Commit ba2ae9e505e3e372e13a3a3ff6acd660d146fb3e in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ba2ae9e505 ] ISIS-2877: generic support for clearing fields > 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)
[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=17520582#comment-17520582 ] ASF subversion and git services commented on ISIS-2877: --- Commit 599102c4937d0d8e35673bea75208cbca35924dc in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=599102c493 ] ISIS-2877: don't allow additional buttons for link to as-if-inline actions > 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)
[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=17520584#comment-17520584 ] ASF subversion and git services commented on ISIS-2877: --- Commit f5a60e286ba14bbddccca7436db7da3d6af2e2dd in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=f5a60e286b ] ISIS-2877: don't allow add. buttons when just viewing > 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)
[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=17520579#comment-17520579 ] ASF subversion and git services commented on ISIS-2877: --- Commit a837d5ee934e6098b503b2be17e8aae09feb7899 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a837d5ee93 ] ISIS-2877: pass Ok/Cancel dialog button captions through translation service > 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)
[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=17520574#comment-17520574 ] ASF subversion and git services commented on ISIS-2877: --- Commit 0589c91311d7f758f9ec987eb405b53ed0405c53 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=0589c91311 ] ISIS-2877: templates: remove superfluous "editing" span > 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)
[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=17520577#comment-17520577 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5dc1d39195113156ff4493b5894825109cf7aa5d in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5dc1d39195 ] ISIS-2877: reinstate fileAccept filter for Blob/Clob > 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)
[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=17520573#comment-17520573 ] ASF subversion and git services commented on ISIS-2877: --- Commit 4c3ab583c2028ac6948ff90b84b428efc42824f4 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=4c3ab583c2 ] ISIS-2877: render '(none)' for all null values when output format > 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)
[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=17520576#comment-17520576 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5237c77a51511ac7543ed40ba67eae07f222e526 in isis's branch refs/heads/ISIS-2957 from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5237c77a51 ] ISIS-2877: edit-prompt-link button-group: show only on hover > 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)
[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=17518276#comment-17518276 ] ASF subversion and git services commented on ISIS-2877: --- Commit e3ce23efcb79c6f068f7780426b1d62822c7ebfb in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=e3ce23efcb ] ISIS-2877: converts Either to an interface - and adds type composition support > 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)
[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=17516891#comment-17516891 ] ASF subversion and git services commented on ISIS-2877: --- Commit a837d5ee934e6098b503b2be17e8aae09feb7899 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a837d5ee93 ] ISIS-2877: pass Ok/Cancel dialog button captions through translation service > 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)
[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=17516889#comment-17516889 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5dc1d39195113156ff4493b5894825109cf7aa5d in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5dc1d39195 ] ISIS-2877: reinstate fileAccept filter for Blob/Clob > 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)
[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=17516892#comment-17516892 ] ASF subversion and git services commented on ISIS-2877: --- Commit 42609533d666b4a8aa6563ec064e0aa1de8f7d20 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=42609533d6 ] ISIS-2877: route clear field click through form-executor > 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)
[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=17516895#comment-17516895 ] ASF subversion and git services commented on ISIS-2877: --- Commit ba2ae9e505e3e372e13a3a3ff6acd660d146fb3e in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ba2ae9e505 ] ISIS-2877: generic support for clearing fields > 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)
[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=17516893#comment-17516893 ] ASF subversion and git services commented on ISIS-2877: --- Commit fd635a12ed2182114ce36a881c3e899492004904 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=fd635a12ed ] ISIS-2877: remove dead code > 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)
[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=17516885#comment-17516885 ] ASF subversion and git services commented on ISIS-2877: --- Commit 4c3ab583c2028ac6948ff90b84b428efc42824f4 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=4c3ab583c2 ] ISIS-2877: render '(none)' for all null values when output format > 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)
[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=17516884#comment-17516884 ] ASF subversion and git services commented on ISIS-2877: --- Commit 3c7e226b4dc3a76fecfc4e4c527b1a0af1ccc6c5 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=3c7e226b4d ] ISIS-2877: revert generic no-click-bubbling fix > 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)
[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=17516898#comment-17516898 ] ASF subversion and git services commented on ISIS-2877: --- Commit da66bae58e6e30aa8e0cabc982c33711ae58772b in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=da66bae58e ] ISIS-2877: Workaround BootstrapFileInputField not reacting to clearing of underlying model. > 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)
[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=17516887#comment-17516887 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5d0ffb95446170d263368d89bea845553bfb2244 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5d0ffb9544 ] ISIS-2877: purge the legacy edit button > 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)
[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=17516881#comment-17516881 ] ASF subversion and git services commented on ISIS-2877: --- Commit cda6234163fd2d67c4ed51d688bbbcbe1f866b2d in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=cda6234163 ] ISIS-2877: output format fix (don't convert) > 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)
[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=17516888#comment-17516888 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5237c77a51511ac7543ed40ba67eae07f222e526 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5237c77a51 ] ISIS-2877: edit-prompt-link button-group: show only on hover > 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)
[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=17516896#comment-17516896 ] ASF subversion and git services commented on ISIS-2877: --- Commit f5a60e286ba14bbddccca7436db7da3d6af2e2dd in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=f5a60e286b ] ISIS-2877: don't allow add. buttons when just viewing > 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)
[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=17516886#comment-17516886 ] ASF subversion and git services commented on ISIS-2877: --- Commit 0589c91311d7f758f9ec987eb405b53ed0405c53 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=0589c91311 ] ISIS-2877: templates: remove superfluous "editing" span > 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)
[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=17516897#comment-17516897 ] ASF subversion and git services commented on ISIS-2877: --- Commit ada56900573999bb735846e3cdd895ac2939 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ada569005e ] ISIS-2877: popover clearing fixes > 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)
[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=17516882#comment-17516882 ] ASF subversion and git services commented on ISIS-2877: --- Commit 023480dc5dec667057b28789db8241a01267adfe in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=023480dc5d ] ISIS-2877: value-type URL: actually render links > 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)
[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=17516878#comment-17516878 ] ASF subversion and git services commented on ISIS-2877: --- Commit 2f3f3ffd050a8a93af0cf8e1391eaa9586cf3cd1 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=2f3f3ffd05 ] ISIS-2877: test fixes (boolean semantics) > 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)
[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=17516894#comment-17516894 ] ASF subversion and git services commented on ISIS-2877: --- Commit 599102c4937d0d8e35673bea75208cbca35924dc in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=599102c493 ] ISIS-2877: don't allow additional buttons for link to as-if-inline actions > 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)
[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=17516880#comment-17516880 ] ASF subversion and git services commented on ISIS-2877: --- Commit b9eab8d36d67aa079157b15c27159787b6fb7427 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=b9eab8d36d ] ISIS-2877: fixes client-side event-bubbling - when link is contained within a component, that has already a click event handler > 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)
[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=17516890#comment-17516890 ] ASF subversion and git services commented on ISIS-2877: --- Commit 99e354208a349dabdcb3bcc9386855c65a5a4361 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=99e354208a ] ISIS-2877: adds support for additional buttons - when hovering over the edit prompt link > 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)
[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=17516883#comment-17516883 ] ASF subversion and git services commented on ISIS-2877: --- Commit a5e8b4fa63c81c75a5efd22c649d085634122e15 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a5e8b4fa63 ] ISIS-2877: generic no-click-bubbling fix > 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)
[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=17516877#comment-17516877 ] ASF subversion and git services commented on ISIS-2877: --- Commit 695cca47762c3b4c16fe9e207b0cd63e405fde92 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=695cca4776 ] ISIS-2877: honor nullable translationService > 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)
[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=17516879#comment-17516879 ] ASF subversion and git services commented on ISIS-2877: --- Commit 10f6fa5412ca5ea01a529c48eecc5b129e43e115 in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=10f6fa5412 ] ISIS-2877: choice dropdown: display (none) for null - also pass choice titles through translation service > 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)
[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=17516876#comment-17516876 ] ASF subversion and git services commented on ISIS-2877: --- Commit c44eb16761ef86fbaf353eab8e49705d4d11bcef in isis's branch refs/heads/master from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=c44eb16761 ] ISIS-2877: pass boolean titles through translation service > 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)
[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=17516874#comment-17516874 ] ASF subversion and git services commented on ISIS-2877: --- Commit da66bae58e6e30aa8e0cabc982c33711ae58772b in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=da66bae58e ] ISIS-2877: Workaround BootstrapFileInputField not reacting to clearing of underlying model. > 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)
[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=17516824#comment-17516824 ] ASF subversion and git services commented on ISIS-2877: --- Commit ada56900573999bb735846e3cdd895ac2939 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ada569005e ] ISIS-2877: popover clearing fixes > 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)
[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=17516803#comment-17516803 ] ASF subversion and git services commented on ISIS-2877: --- Commit f5a60e286ba14bbddccca7436db7da3d6af2e2dd in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=f5a60e286b ] ISIS-2877: don't allow add. buttons when just viewing > 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)
[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=17516797#comment-17516797 ] ASF subversion and git services commented on ISIS-2877: --- Commit ba2ae9e505e3e372e13a3a3ff6acd660d146fb3e in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ba2ae9e505 ] ISIS-2877: generic support for clearing fields > 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)
[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=17516760#comment-17516760 ] ASF subversion and git services commented on ISIS-2877: --- Commit 599102c4937d0d8e35673bea75208cbca35924dc in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=599102c493 ] ISIS-2877: don't allow additional buttons for link to as-if-inline actions > 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)
[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=17516745#comment-17516745 ] ASF subversion and git services commented on ISIS-2877: --- Commit fd635a12ed2182114ce36a881c3e899492004904 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=fd635a12ed ] ISIS-2877: remove dead code > 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)
[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=17516742#comment-17516742 ] ASF subversion and git services commented on ISIS-2877: --- Commit 42609533d666b4a8aa6563ec064e0aa1de8f7d20 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=42609533d6 ] ISIS-2877: route clear field click through form-executor > 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)
[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=17516738#comment-17516738 ] ASF subversion and git services commented on ISIS-2877: --- Commit a837d5ee934e6098b503b2be17e8aae09feb7899 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a837d5ee93 ] ISIS-2877: pass Ok/Cancel dialog button captions through translation service > 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)
[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=17516733#comment-17516733 ] ASF subversion and git services commented on ISIS-2877: --- Commit 99e354208a349dabdcb3bcc9386855c65a5a4361 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=99e354208a ] ISIS-2877: adds support for additional buttons - when hovering over the edit prompt link > 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)
[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=17516239#comment-17516239 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5dc1d39195113156ff4493b5894825109cf7aa5d in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5dc1d39 ] ISIS-2877: reinstate fileAccept filter for Blob/Clob > 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)
[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=17516238#comment-17516238 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5237c77a51511ac7543ed40ba67eae07f222e526 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5237c77 ] ISIS-2877: edit-prompt-link button-group: show only on hover > 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)
[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=17516233#comment-17516233 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5d0ffb95446170d263368d89bea845553bfb2244 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5d0ffb9 ] ISIS-2877: purge the legacy edit button > 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)
[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=17516232#comment-17516232 ] ASF subversion and git services commented on ISIS-2877: --- Commit 0589c91311d7f758f9ec987eb405b53ed0405c53 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=0589c91 ] ISIS-2877: templates: remove superfluous "editing" span > 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)
[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=17516220#comment-17516220 ] ASF subversion and git services commented on ISIS-2877: --- Commit 4c3ab583c2028ac6948ff90b84b428efc42824f4 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=4c3ab58 ] ISIS-2877: render '(none)' for all null values when output format > 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)
[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=17515975#comment-17515975 ] ASF subversion and git services commented on ISIS-2877: --- Commit 3c7e226b4dc3a76fecfc4e4c527b1a0af1ccc6c5 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=3c7e226 ] ISIS-2877: revert generic no-click-bubbling fix > 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)
[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=17515968#comment-17515968 ] ASF subversion and git services commented on ISIS-2877: --- Commit a5e8b4fa63c81c75a5efd22c649d085634122e15 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a5e8b4f ] ISIS-2877: generic no-click-bubbling fix > 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)
[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=17515950#comment-17515950 ] ASF subversion and git services commented on ISIS-2877: --- Commit b9eab8d36d67aa079157b15c27159787b6fb7427 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=b9eab8d ] ISIS-2877: fixes client-side event-bubbling - when link is contained within a component, that has already a click event handler > 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)
[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=17515938#comment-17515938 ] ASF subversion and git services commented on ISIS-2877: --- Commit 10f6fa5412ca5ea01a529c48eecc5b129e43e115 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=10f6fa5 ] ISIS-2877: choice dropdown: display (none) for null - also pass choice titles through translation service > 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)
[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=17515930#comment-17515930 ] ASF subversion and git services commented on ISIS-2877: --- Commit 695cca47762c3b4c16fe9e207b0cd63e405fde92 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=695cca4 ] ISIS-2877: honor nullable translationService > 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)
[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=17515931#comment-17515931 ] ASF subversion and git services commented on ISIS-2877: --- Commit 2f3f3ffd050a8a93af0cf8e1391eaa9586cf3cd1 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=2f3f3ff ] ISIS-2877: test fixes (boolean semantics) > 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)
[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=17515925#comment-17515925 ] ASF subversion and git services commented on ISIS-2877: --- Commit c44eb16761ef86fbaf353eab8e49705d4d11bcef in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=c44eb16 ] ISIS-2877: pass boolean titles through translation service > 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)
[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=17515913#comment-17515913 ] ASF subversion and git services commented on ISIS-2877: --- Commit 6601707ff568b1bd61d238512851b54908fd27ff in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=6601707 ] ISIS-2877: starting to add i18n support for wkt tooltips and labels > 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)
[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=17515908#comment-17515908 ] ASF subversion and git services commented on ISIS-2877: --- Commit b83bf81befa973fd2a7c0ca311424c4ab4278784 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=b83bf81 ] ISIS-2877: fixes serialization issue with Clob FileUploadModel > 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)
[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=17515904#comment-17515904 ] ASF subversion and git services commented on ISIS-2877: --- Commit 578b74fe1629973b3982ce78f8a26df00910b317 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=578b74f ] ISIS-2877: working on Blob?Clob panel fixes > 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)
[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=17515851#comment-17515851 ] ASF subversion and git services commented on ISIS-2877: --- Commit a8eacb277dab9b0e51a4601fdaad22395792e042 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a8eacb2 ] ISIS-2877: revert prev. commit - instead add new choices mixin for optional property > 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)
[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=17515843#comment-17515843 ] ASF subversion and git services commented on ISIS-2877: --- Commit 354a29d93c8664253f0de45a9be72643c840038a in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=354a29d ] ISIS-2877: demo: fixes param optionality for WrapperBooleanHolder_updateReadOnlyPropertyWithChoices > 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)
[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=17515835#comment-17515835 ] ASF subversion and git services commented on ISIS-2877: --- Commit 31b368dc0d57c5526b9271ff45a8fe524561a87e in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=31b368d ] ISIS-2877: css: breadcrumb fix (part 2) > 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)
[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=17515830#comment-17515830 ] ASF subversion and git services commented on ISIS-2877: --- Commit 59f2c7bb72444d779ac93a6b7aa8957e56bf2e44 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=59f2c7b ] ISIS-2877: wkt css: boolean 3-state fixes > 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)
[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=17515719#comment-17515719 ] ASF subversion and git services commented on ISIS-2877: --- Commit fb17bbe3f598d8207df871a0386cf4b9e9859cd5 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=fb17bbe ] ISIS-2877: css fixes: icon&title + breadcrumbs > 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)
[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=17514560#comment-17514560 ] ASF subversion and git services commented on ISIS-2877: --- Commit 3d32e3034940073344cc3b7e76018fc20dba in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=3d32e30 ] ISIS-2877: composite value-type semantics providers need a DefaultsProvider - also adds support for per feature customization > 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)
[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=17514553#comment-17514553 ] ASF subversion and git services commented on ISIS-2877: --- Commit eac9e25792c2dd9b7446cbe107f227f5b234e23e in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=eac9e25 ] ISIS-2877: fixes optional Properties/Parameters not handled when null (UI) > 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)
[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=17514424#comment-17514424 ] ASF subversion and git services commented on ISIS-2877: --- Commit e614217ba2af7a71558d57ae1ee4b0820230cea0 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=e614217 ] ISIS-2877: don't init property negot. value with default when empty but not mandatory > 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)
[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=17514020#comment-17514020 ] ASF subversion and git services commented on ISIS-2877: --- Commit 12639f5cf96dbac3a5833451997b3a9ccc8bfeeb in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=12639f5 ] ISIS-2877: adds new member search scope MixedIn.ONLY > 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)
[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=17514012#comment-17514012 ] ASF subversion and git services commented on ISIS-2877: --- Commit 02c918076135294e5890a5f65b270bbfd15f46d3 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=02c9180 ] ISIS-2877: let composite-value-mixin names correspond to qualifier names - in support of per feature customization > 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)
[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=17513540#comment-17513540 ] ASF subversion and git services commented on ISIS-2877: --- Commit d6a26b0c0f900b413544fb9963eecae9e7e93f93 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=d6a26b0c0 ] ISIS-2877: properly setting up a readonly FormComponent as receiver for nested dialog results > 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)
[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=17513413#comment-17513413 ] ASF subversion and git services commented on ISIS-2877: --- Commit 75fc07c64392bf89ee4fb4d3aa0e38146dd4df0f in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=75fc07c ] ISIS-2877: properly detect the scenario when param needs nested editing dialog > 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)
[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=17513241#comment-17513241 ] ASF subversion and git services commented on ISIS-2877: --- Commit 67343f07b74c1e69dfbcb9daa34efec29859de7f in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=67343f0 ] ISIS-2877: revert breaking change from last commit > 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)
[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=17513238#comment-17513238 ] ASF subversion and git services commented on ISIS-2877: --- Commit 638e53320eedba58ca9275643593517749a4ec05 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=638e533 ] ISIS-2877: adds the backend for composite value update on params > 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)
[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=17513197#comment-17513197 ] ASF subversion and git services commented on ISIS-2877: --- Commit fc851e6192733dd61f7ad21c7b35a80030de5fa5 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=fc851e6 ] ISIS-2877: CompositeValuePanel: render in output format (no input) > 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)
[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=17513163#comment-17513163 ] ASF subversion and git services commented on ISIS-2877: --- Commit ab1cc45dc5a8833d7c69b83240a8496ba947ff89 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ab1cc45 ] ISIS-2877: factor out scalar panel for composite values > 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)
[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=17513036#comment-17513036 ] ASF subversion and git services commented on ISIS-2877: --- Commit 47cd7d178c63dfd1580659cf85e4b28b937004a9 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=47cd7d1 ] ISIS-2877: mm: honor paramIndex in Identifier's toString() and equals() > 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)
[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=17513014#comment-17513014 ] ASF subversion and git services commented on ISIS-2877: --- Commit 89f47115c9f6beefdd84b7b95dcf2bad4e86ff3c in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=89f4711 ] ISIS-2877: wkt: swap args in ComponentFactoryRegistry.createComponent for consistency > 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)
[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=17513013#comment-17513013 ] ASF subversion and git services commented on ISIS-2877: --- Commit bf88ca9a7c2030fe085518a75f97677a6fd5c0ac in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=bf88ca9 ] ISIS-2877: commons: fixes Proxy toString() delegation > 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)
[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=17512997#comment-17512997 ] ASF subversion and git services commented on ISIS-2877: --- Commit 4ad911e9179d968497cae65640dfd3d5eb97f6e5 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=4ad911e ] ISIS-2877: create UI Component (ActionLink) for LinkAndLabel only when needed - simplifies ScalarModel utilities > 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)
[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=17512938#comment-17512938 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5c7c4ea01b74495968f825c03461b07d1c9fb364 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5c7c4ea ] ISIS-2877: fixes PromptStyle INLINE not used for actions associated to properties > 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)
[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=17512869#comment-17512869 ] ASF subversion and git services commented on ISIS-2877: --- Commit 05a0bccbda9db2178ead5a765070428b5e34617e in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=05a0bcc ] ISIS-2877: purge intermediate CalendarEvent demo mixin - no longer needed > 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)
[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=17512865#comment-17512865 ] ASF subversion and git services commented on ISIS-2877: --- Commit e2c2748af0925306a6c44a086c5e881839dd4626 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=e2c2748 ] ISIS-2877: human readable title for CalendarEvent > 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)
[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=17512864#comment-17512864 ] ASF subversion and git services commented on ISIS-2877: --- Commit 22eb7efe5f7902d93ea56f8b0417628570c1c6aa in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=22eb7ef ] ISIS-2877: CSS: introduce card format modifier: mini-card > 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)
[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=17512852#comment-17512852 ] ASF subversion and git services commented on ISIS-2877: --- Commit aec53e678e0a14aae28974f3cdfb678dd0e24ea8 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=aec53e6 ] ISIS-2877: use html template for CalendarEvent compact rendering > 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)
[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=17512851#comment-17512851 ] ASF subversion and git services commented on ISIS-2877: --- Commit 8d7ad29a68af081386de6711c79f6de74956f1b0 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=8d7ad29 ] ISIS-2877: minor utility refactoring > 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)
[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=17512679#comment-17512679 ] ASF subversion and git services commented on ISIS-2877: --- Commit 5cf67063df793863aab2efd9713d5d871ecf1a60 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=5cf6706 ] ISIS-2877: cleanup and javac compile fixes > 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)
[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=17512588#comment-17512588 ] ASF subversion and git services commented on ISIS-2877: --- Commit 48ddb5e23df155f6681a843d7817cf9c143111b7 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=48ddb5e ] ISIS-2877: proof of concept: we can now edit properties that are of composite value type - mapping the composite-value type mixin result back to the receiving domain-object's property was rather challenging - had to introduce dynamic proxies to get that working > 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)
[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=17512440#comment-17512440 ] ASF subversion and git services commented on ISIS-2877: --- Commit 0348e957388218f022a986a4d7aec7c2ed6d7dea in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=0348e95 ] ISIS-2877: inline prompt creation fixes - only create when container fragment actually supports it - otherwise partial page updates will fail > 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)
[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=17512370#comment-17512370 ] ASF subversion and git services commented on ISIS-2877: --- Commit da20dc6558448b333d8e376eff3ce0fc4b9f74b4 in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=da20dc6 ] ISIS-2877: revert breaking template change > 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)
[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=17512365#comment-17512365 ] ASF subversion and git services commented on ISIS-2877: --- Commit 65e67edf32f887f5b3a63d57fed6bf79229dae5b in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=65e67ed ] ISIS-2877: css fixes > 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)
[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=17512352#comment-17512352 ] ASF subversion and git services commented on ISIS-2877: --- Commit ae2ea58866fb6b4305f3fb87e9e4e9d21cd2605d in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ae2ea58 ] ISIS-2877: MM: properly report ActionLayout.Position for managed actions > 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)
[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=17512282#comment-17512282 ] ASF subversion and git services commented on ISIS-2877: --- Commit 1cedc585b0605dc95ccf8de9e04626f4c3421cfe in isis's branch refs/heads/2877_value.comps from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=1cedc58 ] ISIS-2877: cleanup superfluous code > 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)
