It seems to me that if you want a fixed portlet in a fixed location on the page, the best approach would be to embed it in the template as a macro/include rather than implementing it as a portlet. Would there be any advantage to making it an actual portlet? Unless of course you did want the user to be able to move it around on the page.
Comments? Mark On Wed, 2002-02-06 at 17:18, Paul Spencer wrote: > Brian, > I see this as a very useful feature. Some question on how you would use > and maintain a "locked" portlet > > 1) How would parameter on the portlet be maintained? > > 2) Would the user be allowed to reposition the portlet in their portal? > > 3) Do you envision a adding and removing these portlets from existing user? > > Paul Spencer > > Brian Keller wrote: > > > Is it possible to lock a portlet for a set of users so they always > see it? I > > know this goes against the typical usage of jetspeed, but it is a > necessary > > feature for us. > > > > Thanks, > > Brian > > > > -- > > 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]>
