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

Erik de Hair commented on ISIS-800:
-----------------------------------

Hi Dan,

I finally had some time to play around with the wizard. Here are some issues I 
noticed:
- My app does show an edit button below a states' form (while the documentation 
doesn't) and I have to click it to edit the current state. Otherwise the fields 
are disabled. I think the way like shown in the documentation on GitHub 
(without edit button) is the most user friendly.
- When a state has a required field and I click 'next', no validation gets 
triggered.

By the way: I'm using Isis-1.7.0 with wizard-1.8.0-SNAPSHOT because I wanted to 
try a real world example for my company (is that a problem?).

Erik

> 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.3.4#6332)

Reply via email to