You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Brian Keller <bk...@newsouth.com> on 2002/02/06 20:59:43 UTC
making portlets always visible for new users
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: making portlets always visible for new users
Posted by Ming Fai <mi...@hongkong.com>.
i see an advantage. Long time ago, I've considered how should I implement a
navigation menu in Jetspeed. The current proper way is to use template file
(e.g. /templates/jsp/navigations/html/left.jsp) and just like the following:
+------------------+
| NB | PL PL |
| NB | |
| | PL PL |
|?PL?| |
| | |
+------------------+
NB - Navigation bar
PL - Portlet
?PL? - Portlet that cannot be implemented in the current Jetspeed
however, a drawback is, I cannot put a portlet *under* the Navigation bar.
i.e. the "PL?". If there fixed portlet is available, then I can use it to
implement navigation menu as well as putting portlets under the menu. Do ppl
need to put portlets under the navigation bar? I see a general usage which
is to make banner ad portlet (link to an Ad mgmt system). It's common to see
AD in both the left hand side under nav. bar and right hand side. e.g.
http://www.javaworld.com/
Another key point is flexibility. If there is fixed portlet, then I do not
need to rely on the turbine templating model. (it's a good MVC model, but
not necessarily fit everybody's need) I always think Jetspeed should be the
implementation of Portlet API and should be independent of any framework.
how do you think?
regards,
mingfai
-----Original Message-----
From: Mark Nutter [mailto:javadev@linklore.org]
Sent: Thursday, February 07, 2002 8:17 AM
To: Jetspeed Users List
Subject: Re: making portlets always visible for new users
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:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: making portlets always visible for new users
Posted by Mark Nutter <ja...@linklore.org>.
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:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: making portlets always visible for new users
Posted by Paul Spencer <pa...@apache.org>.
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:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>