Yes, I misjudged your question.
The various link components do not have a formal target
parameter, but they support informal parameters.
In your example, a link in frame A will change the
content of frame B.
Frame A's HTML:
<a target="frameB" jwcid="direct"> ...
Page A's listener method:
public void changeFrameB(IRequestCycle cycle)
{
// Do some business logic ...
cycle.setPage("PageB");
}
The rest of this reply is probably review to you, but
maybe not to others ...
The sticking point is that the listener is in Page A,
even though the effect is visible in frame B and
eventually causes page B to be rendered (in frame B).
Clicking the link in Frame A (containing Page A),
invokes a listener method on Page A. That is the
Tapestry way.
Now, that listener method which exists to support that
menu bar link (in Page A), knows that it was submitted
with a target into frameB. Therefore, after doing
business methods and presumably interacting with Page B,
it directs the request cycle to render page B as the
response page.
Page B renders, and the resulting HTML replaces the
content in frameB.
--
[EMAIL PROTECTED]
http://tapestry.sf.net
> Howard:
>
> I've read your reply a couple of times and unless I'm being totally dense
> (possible), you've responded with something that has nothing to do with my
> original question. I'm familiar with the fact that I can use frames with
> Tapestry. I'm doing that now (see the example I included with the post that
> Geoff responded to). What I really want to know is whether an action that
> takes place in one frame can easily be redirected to another. For example,
> two frames, each a Tapestry Page:
>
> _______________________________
> | menu |
> |_______________________________|
> | content |
> |_______________________________|
>
> Several buttons appear in the menu:
>
> _______________________________
> | item1 | item2 | item3 |
> |_______________________________|
>
> Press item1 and the Item1 page shows up in the content frame. Same for
> item2, etc.
>
> If I'm using straight html, I can include a target attribute in either my
> anchor specification or in the base href for my page and the correct page
> appears in the content frame. My impression is that Tapestry (a) ignores
> the content of the anchor markup and (b) provides its own base href via the
> shell component. Looking at the Tapestry docs I see nothing that leads me
> to believe that a link (Tapestry's equivalent of an anchor, yes?), or the
> Tapestry supplied base href can specify a target frame. No doubt there are
> some things that can be done to address this issue, but shouldn't it be as
> straight-forward as binding a 'target' parameter for a component link?
>
> Forgive me if I'm totally missing the boat here. I'm questioning my sanity
> after reading your response. Maybe it is all obvious and I'm the only one
> who can't see it. Its a Bad Day at Black Rock if so.
>
> Prepared to eat crow,
>
> Craig
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
