I understand what you want, and with more thought I believe you are right that a refresh button on the portlet titlebar would be worthless. I think the refresh button inside the IFrame is one of the options. You may want to explore some of options of setting auto-refresh in the header of a customized IFrame portlet with <META HTTP-EQUIV="Refresh" CONTENT="5;URL=http://www./your_host.com/your_site/your_page.html";>.
In Jetspeed, I do not know how you would refresh one portlet and not others on the same page, without using IFrames. I thought an applet portlet might work, but discovered the applet will reset during a refresh. What portal engine have you seen that supports drag-resize and selective refresh? Glen Yesberg, John wrote: > Glen, > > Thanks for the suggestion. Yes, I've looked at IFrames. From what I can > see, an IFrame has the same functionality as a Frame, but they have different > geometrical characteristics on the screen. > > If I was using the IFramePortlet as currently provided, then the portlet title > bar buttons (config, minimise, maximise, restore) would be outside the IFrame. > In fact, if one pushes any of those buttons, the whole page (including all of > the other portlets) is reloaded. I'm trying to allow just the one portlet to > be reloaded/refreshed, without disturbing the other portlets. That means that > I would need to have my refresh button *inside* the IFrame - but that's ok. > > I think IFrames would be a good solution except for my drag-resize requirement. > It would allow one to continue to use the current set of controllers, which use > tables as the layout mechanism, rather than the rather clumsy frames mechanism. > It would still be necessary for the browser to make separate get requests for > each of the portlets to go in the IFrames, which would need some modification > to jetspeed, I think. > > John. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
