[CAUSEWAY-810] Remove Wizard and Wicket viewer implementation on basis that shouldn't constrain programming model to this extent.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: viewer-wicket-1.6.0, core-1.6.0
• Component/s: Viewer Wicket
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 14/Jun/14 09:01
• Updated: 28/Jul/14 13:35
• Resolved: 16/Jun/14 10:29

Description

ie, the work committed in ISIS-800 and ISIS-807.

Instead, should be a separate "add-on"?

Background:

• Jeroen made this suggestion; he thinks that the Wizard interface is too prescriptive
• However Oscar thinks that we should provide a default implementation.

~~~
NB: if we do decide to remove the Wizard from IsIs, then Jeroen and I have registered the "isisaddons.org" domain and the github.com/isisaddons as a domain home for such add-ons.

The idea is to nurture something similar what Apache Wicket do with their "wicketstuff" companion site. All of my com.danhaywood wicket extensions could then move to isisaddons.org.

Issue Links

• is related to: CAUSEWAY-800 Wizard-like form for Wicket viewer
• is related to: CAUSEWAY-807 Break out EntityPropertiesForm into two for the new IWizard, and then make into a separate component.
• links to: https://github.com/danhaywood/isis-wicket-wizard