You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Marilen Corciovei <le...@nemesisit.rdsnet.ro> on 2003/06/04 15:49:14 UTC

problem: how to avoid inconsistencies when a user open a link in a new window

I am having problem with users opening a link in a new window. I tried
to store specific navigation data in the visit but this result in
inconsistencies. My ideea was to make all the links carry some data as
parameters. Can this be done in some way without modifind every
component?

Please, can anyone give a hint, Len

> Hello,

> I am working since apx 6 months with tapestry. Until now everyting was
> more or less ok but I have reached a problem I can not solve. I have a
> report tree with tables and other elements. This require that each >
page
> keeps some information not on server side since I want to enable
> shift_click open in a new window and I can not keep things in the
visit.
> I tried to have the needed parameter sent using
> cycle.setServiceParameters but the pages might contain forms, tables
or
> other type or links which will not pass on this parameter and I do not
> want to rewrite the table sort and all the forms for example. Is there
a
> common used solution for that problem? Can anybody help?

> Len


-- 
Marilen Corciovei <le...@nemesisit.rdsnet.ro>


Re: problem: how to avoid inconsistencies when a user open a link in a new window

Posted by Marilen Corciovei <le...@nemesisit.rdsnet.ro>.
Thanks for your response the problem is as follows:

assume I have a page which gets some parameters, it uses them to render
itself. The page also contains a table component. When the user clicks a
table column which is a DirectLink this one will call the page again but
with the original parameters lost. I am trying to find a way not to be
forced to modify the table column to send the original parameters also.
I was thinking of extending DirectService. I know how to handle
parameter sending with my own links but not with others from existing
components and I hope not to rewrote them.

Len

On Wed, 2003-06-04 at 17:11, Bill Lear wrote:
> On , June 4, 2003 at 16:49:14 (+0300) Marilen Corciovei writes:
> >I am having problem with users opening a link in a new window. I tried
> >to store specific navigation data in the visit but this result in
> >inconsistencies. My ideea was to make all the links carry some data as
> >parameters. Can this be done in some way without modifind every
> >component?
> >
> >Please, can anyone give a hint, Len
> 
> Not sure about this: when someone clicks on a link, why not have
> a listener that responds to the click.  It knows which page to
> select, and you can retrieve that page and set whatever you
> need to in it and then activate it:
> 
>     public void myListener(IRequestCycle cycle) {
>         MyPage page = (MyPage) cycle.getPage("MyPage");
> 
>         page.setThings(getThingsFromSomewhere());
> 
>         cycle.activate(page);
>     }
> 
> 
> Bill
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
-- 
Marilen Corciovei <le...@nemesisit.rdsnet.ro>


Re: problem: how to avoid inconsistencies when a user open a link in a new window

Posted by Bill Lear <ra...@zopyra.com>.
On , June 4, 2003 at 16:49:14 (+0300) Marilen Corciovei writes:
>I am having problem with users opening a link in a new window. I tried
>to store specific navigation data in the visit but this result in
>inconsistencies. My ideea was to make all the links carry some data as
>parameters. Can this be done in some way without modifind every
>component?
>
>Please, can anyone give a hint, Len

Not sure about this: when someone clicks on a link, why not have
a listener that responds to the click.  It knows which page to
select, and you can retrieve that page and set whatever you
need to in it and then activate it:

    public void myListener(IRequestCycle cycle) {
        MyPage page = (MyPage) cycle.getPage("MyPage");

        page.setThings(getThingsFromSomewhere());

        cycle.activate(page);
    }


Bill