You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/07/16 19:54:05 UTC
[jira] [Updated] (ISIS-810) Remove Wizard and Wicket viewer
implementation on basis that shouldn't constrain programming model to this
extent.
[ https://issues.apache.org/jira/browse/ISIS-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-810:
-----------------------------
Component/s: Viewer: Wicket
> Remove Wizard and Wicket viewer implementation on basis that shouldn't constrain programming model to this extent.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-810
> URL: https://issues.apache.org/jira/browse/ISIS-810
> Project: Isis
> Issue Type: Improvement
> Components: Viewer: Wicket
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.6.0, core-1.6.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)