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. -----Original Message----- From: Glen Carl [mailto:[EMAIL PROTECTED]] Sent: Friday, 11 October 2002 3:09 To: Jetspeed Users List Subject: Re: A portal using frames instead of tables Have you experimented with the IFrame portlets? They do not have the dragging resize capability, but they provide some really nice separation between the portlet application and the portal. For your particular needs, you may want to add refresh actions within your portlet applications, so you can refresh the application of interest without affecting the other portlets. I would guess another icon could be added to the portlet title bar to have a refresh for your portlet. Glen Yesberg, John wrote: > Hello, > > I had a couple preconceived notions about how portals might work before I installed >and began to play with jetspeed. > > 1. I thought it might be possible to resize various portlets by dragging on the >border. > 2. I thought that portlets might be able to update themselves independently of >others. For example, consider two portlets. I'm in the middle of typing an essay into >a form in one portlet. Before clicking "submit" on that portlet, I want to click >"refresh" on the other to get the latest stock price, or some other value out of a >database. But when I do that, the *whole* page refreshes (not just that portlet), so >I lose all the info I'd just typed. > > I think that these features would be possible of portlets were displayed using >frames rather than as elements within a table. I can imagine that there would be >disadvantages of this approach (eg. needing a separate HTTP Get for each portlet, >plus one for each layout controller), but maybe the advantages would outweigh them >for some situations. > > Has anyone else thought of this? Implemented it? Do any other Portal products out >there do this sort of thing? Are there serious disadvantages that I haven't thought >of? My colleague is considering writing a controller class that does this, and we'd >be interested in your collective wisdom. > > Thanks, > > John. > -- > Dr John Yesberg TCS Group, ITD, DSTO > DJFHQ, Gallipoli Barracks, Ph. (07) 3332 7664 > Enoggera, Qld. 4051 Fax (07) 3332 5056 > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
