On 17 February 2013 14:35, Christian Steinebach < [email protected]> wrote:
> Hi! > > Based on Dan's extensions and heavy cut'n paste etc... I managed to > build an extension which displays a popup window with an external link. > Problem is the extension first creates a link which then has to be clicked > to show the external page. So there is one link too much in the chain. ;-) > > Here is the code: > https://github.com/chris58/isis-wicket-popupbox.git > > If anybody has an idea for how to let the extension pop up the window > without > the use of an ExternalLink please let me know. :-) > > How about a bit of Javascript which could fire on the document ready event and click the link for you? In Wicket it is possible to add HeaderContributors so that the necessary Javascript is rendered in the page. That said, with respect to what you're aiming to do here, I should mention that one thing I need to spend some time on in the next few weeks is in improving the Wicket viewer's support for providing feedback to the user. As you might have noteiced, in Isis the injected DomainObjectContainer has the "informUser", "warnUser" and "raiseError" methods (in increasing levels of severity). The viewer is meant to look for these messages and render them appropriately to the user. My current plan was for: - informUser to be shown as some sort of toast/growl notification - warnUser to be rendered on the page in a feedback panel - raiseError to be rendered as a modal dialog that requires acknowledgement If you (or anyone else) have any thoughts on this, let me know. Dan > Regards > Christian >
