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

ASF subversion and git services commented on ISIS-800:
------------------------------------------------------

Commit 73050278c715cadaf1938f6a680c5cd562b96154 in isis's branch 
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7305027 ]

ISIS-800: improvements to the wizard

... sorted out that issue with drop-down choices not being disabled (was a bug 
in ValueSelect2ChoicesPanel, not in EntityPropertiesForm itself)

Also:
- extended the ToDoItemWizard to demonstrate
- refactored/improved/better documented the Wicket viewer's use of the Wicket 
event bus (even though it turns out that I didn't need to use it in order to 
fix the issue...).


> Wizard-like form for Wicket viewer
> ----------------------------------
>
>                 Key: ISIS-800
>                 URL: https://issues.apache.org/jira/browse/ISIS-800
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core, Viewer: Wicket
>    Affects Versions: viewer-wicket-1.5.0, core-1.5.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: viewer-wicket-1.6.0, core-1.6.0
>
>
> Erik Hair on [email protected]:
> Is it in some way possible to create a wizard like form or open an action 
> with an action? I tried to return a not yet persisted object from an action 
> and hoped I could edit some properties and add some elements to collections 
> of the object before persisting it to the database...
> ~~~~~~
> Dan:
> Short answer is that we don't really (properly) support this.  And we should.
> I agree that @NotPersistable is confusing and its not clear what to use; the 
> right solution would be to implement a view model (currently: implement the 
> ViewModel interface), and then - optionally - write a custom ComponentFactory 
> for the Wicket viewer to render the wizard appropriately.
> But the snag even with the above is that (currently) view models are 
> immutable; they support actions but their properties cannot be edited.
> I can see the way forward on this; I don't think it's difficult, but it will 
> require a change in core and probably the wicket viewer also.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to