Hi,
it sounds like iframes are like frames. if that's the case, eelco
has described what you should do.
yes, iframes are almost like frames, except there is a normal page
around them. Eelco suggested being careful about the expiration of
pages and how to get around this using PageMaps. Got that. But this
doesn't help a lot with using iframes in a component oriented way.
Maybe it's a bit hard to imagine why I want to do this. Please have a
look at the static html mock-up (works in firefox/safari with js only):
http://www.dreivier.net/columns/
(I know this is a mean example, but I thought I should choose
something tricky for trying out a new web component framework :)
If it is a "link" to another page, why not just use a wicket Link
component?
I tried that and it works very well. I just took the Link/PageLink
class and created a Frame class using ILinkListener for handling the
iframe request. I added a third constructor for passing a Page object
instead of a Class so I get the same Page when called from the same
Page instance every time. I don't know if this gets me into trouble
later on (because it's somehow like embedding a WebPage), but for now
this seems to be fine.
The only thing bugging me is the page expiration when having more
than 10 pages. I know, PageMaps. But is there maybe another way to
control the page expiration? In my case I would like to have these
Pages expiring only and exactly when the containing page expires - a
behavior which can be achieved hardly with PageMaps...
Regards,
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
