Matej Knopp-2 wrote:
>
> Hi, i think it should be possible to accomplish.
>
> Put the next/previous links to the page with the tree. Hide them (e.g.
> putting inside <div style="display:none"/>
>
> Then on the top page in your prev/next links (in the javascript
> handler) you need to find the corresponding link element in the tree
> frame and call it's onclick handler.
>
> -Matej
>
Ha! That's clever! :)
Just to be sure I understand. You are suggesting I modify the links in my
header frame to not actually do anything except call hidden next and
previous links in the navigation frame. Is that right?
So that would seem to require javascript in those header next/previous
links. As I'm sure you can tell, I'm still pretty new when it comes to
Wicket. What would be the appropriate way to add that javascript? I've read
hear and there that typically that kind of thing is added via Behaviors. Is
that right? Or is it preferable to do something like:
add(new AjaxLink("nextLink") {
public void onClick(final AjaxRequestTarget target) {
target.appendJavascript("parent.nav.clickNextLink()");
}
});
Matt
--
View this message in context:
http://www.nabble.com/Link-on-one-frame-modifying-component-on-another-tf4213856.html#a11989365
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
