"Thomas F. Boehme" wrote:
>
> Raphael,
>
> A maximize may want to re-load certain content, a close may have free up
> some resource, etc. It wouldn't be the portlet itself doing those things,
> but rather an event listener that the portlet can attach to the portlet
> control. Does that make sense?
>
Yes definitely.
> The thing that mentioned below is required too! That's the "what does the
> portlet allow" aspect of window-management, which I would attach to portlets
> rather than portlet controls. For example, an advertisement portlet should
> be non-closeable for all PSMLs. Therefore, those restrictions should be
> placed with the portlet registration.
>
Are you sure that an advertisement portlet will always want to be non
closeable ? This is in my opinion a decision to be made by the
portal administrator, not the portlet developper and thus should be
set/get independantly of the Portlet itself.
Basically, I'd say:
Portlet API = developer realm
Registry = system administrator realm
User PSML = user/sysadm realm
By this logic, I'd support extending the registry syntax to let
the administrator decide whether a portlet should always be visible.
Does that makes sense to you ?
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
