I believe what he needs is must finer grained update then refreshing
all pages. Fortunately, since the pages originate from same site, it
is possible to do using little bit of javascript.
-Matej
On 8/3/07, davor-x <[EMAIL PROTECTED]> wrote:
>
> I think you need to refresh the frameset page.
> The link that updates framed windows should have the target attr set:
> target="_top". Handle the onClick in wicket and use setResponsePage(your
> frameset page). The in the frameset page, setup the src attributes for your
> frames.
>
> There is also a wicket example somewhere about links, frames, tragets..
> Bye
>
>
> Watter wrote:
> >
> > I'm not a fan of frames, but in this particular situation, I don't have a
> > lot of control over the the content that's displayed in one of the frames
> > so I need to keep it separate from the rest of the application.
> >
> > I have three frames. A header frame that stretches all the way across the
> > top, a navigation frame below the header on the left, and a content frame
> > below the header on the right. The header and navigation frames contain
> > standard wicket driven pages and the content frame will usually hold
> > external HTML content.
> >
> > The navigation frame contains a Tree component. The Header contains links
> > for 'Next' and 'Previous'. A user can navigate either by clicking one of
> > the items in the tree or by clicking Next or Previous in the header.
> >
> > I've got the actual navigation working. When someone clicks Next,
> > Previous, or a tree item, the content frame goes to the right place.
> > However, I can't seem to figure out a way to update the Tree's visual
> > indication of which node is selected when I click Next or Previous in the
> > Header. I thought that perhaps some javascript magic might take place if I
> > passed my navigation page (called 'nav' int he code below) to the header
> > frame, and then did something like:
> >
> > add(new AjaxLink("nextLink") {
> >
> > public void onClick(final AjaxRequestTarget target) {
> > target.addComponent(nav.getLearningItemTree());
> > nav.getLearningItemTree().getTreeState().selectNode(nextNode,
> > true);
> > }
> > });
> >
> > Well, this does actually update the backed of the Tree component, but the
> > actual visual representation of the tree in the navigation frame doesn't
> > get updated. Of course, if I put the same Next link actually ON the
> > navigation frame page, then it works as expected.
> >
> > So, it seems like this should be possible, somehow. The link on the
> > navigation page is simply a javascript call. I should be able to make that
> > same call from the header frame by means of a "parent.nav.xxxxx", but I
> > can't figure out what that xxxxx should be. Or maybe there's a call that
> > will simply refresh that tree component, or parts of it.
> >
> > Any ideas?
> >
> > Matt
> >
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Link-on-one-frame-modifying-component-on-another-tf4213856.html#a11988055
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
