The modal dialog really improves the usability, thanks Dan. I've attached attached a screenshot which tells more then thousand words.
I just recently learned that you can use java.lang.Object as the return type of an action and return whatever domain object or collection you programmatically decide. So your action basically is the controller. Nice! Sounds familiar to what Oscar is doing. Cheers, Jeroen On Mon, Dec 2, 2013 at 7:37 PM, GESCONSULTOR - Óscar Bou < [email protected]> wrote: > > > Good done. > > We also use modal dialogs on our custom viewer to avoid context switching. > The same dialog redirects to a Domain Object if that's the result of the > action invocation, or currently shows a Collection in a grid on the same > dialog if that's the result of the action. The user can then navigate to > any of the objects in the collection. > > > > El 02/12/2013, a las 17:54, Dan Haywood <[email protected]> > escribió: > > > Hi folks, > > > > just an fyi that I've committed and pushed ISIS-486 [1], to render the > > Wicket viewer's action prompts in modal dialogs. This should make for a > > better overall user experience. > > > > To use, you'll need to build from source, as per [2]. > > > > In case there are issues, the old behaviour (action prompts on their own > > page) can be enabled by adding the following property: > > > > isis.viewer.wicket.disableModalDialogs=true > > > > into WEB-INF/viewer_wicket.properties (or isis.properties if you prefer). > > I'll probably remove this original behaviour before pushing out a final > > release, though. > > > > Cheers > > Dan > > > > > > [1] https://issues.apache.org/jira/browse/ISIS-486 > > [2] http://isis.apache.org/contributors/building-isis.html > >
