Watch your session space though; each page instance will be stored in
the session. This doesn't have to be a problem though, but you should be
especially carefull when the expiration of pages. You could best have
each IFrame use each own PageMap. Each page map is hold in the session
seperately, so any frame's page will not be the cause of expiration of
another frame's page.
The only thing you have to do to assign a page map is to have it in your
url (in your case the (I)Frame url that points to the first bookmarkable
page you start with), like:
http://localhost:8080/wicket-examples/navomatic?pagemap=topFrame&bookmarkablePage=wicket.examples.navomatic.Page2
where the page map is 'topFrame'. After this, all subsequent links etc
will use the page map.
Read more about page maps in the javadocs of wicket.Page
Eelco
Igor Vaynberg wrote:
You could easily accomplish all these things in wicket if you werent using
iframes. I think to get it working with iframes is going to take a lot of
experimentation on your part.
Since iframes exist in the browser as independent pages im not sure if
versioning of the container page would make any sense for the back button
support; especially since that page will not refresh and is unaware of any
user interaction inside the iframes.
Igor
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ralf Ebert
Sent: Friday, June 24, 2005 5:18 PM
To: [email protected]
Subject: Re: [Wicket-user] WebPage and iframes
Hi,
one in the other from wicket's perspective, iframes are independent
pages and so the content of your iframe will not be part of the
component hirarchy of the container page.
yes, that's right. But what I want to do is having the content of the
iframes managed as component of the container page. Basically what I want to
do is have a List of WebPages which are rendered as iframes, because the
iframes are added and removed in a very dynamic way from the containing page
(I'm using this for a kind of very special site rendering, not for embedding
one or two iframes in a page in static way). Also I want to have the state
of the iframe component hierarchy linked to the container page component
hierarchy so I can use Wicket features like painless browser-back even for
this complex behavior.
I'm just wondering if this can be done in a clean component-oriented way
without using independent Pages at all...
Ralf
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from
IBM. Find simple to follow Roadmaps, straightforward articles, informative
Webcasts and more! Get everything you need to get up to speed, fast.
http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
