> -----Original Message-----
> From: Raphael Luta [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 10. November 2000 17:02
> To: JetSpeed
> Subject: Re: editable portlets for release 1.2
>
>
> "Thomas F. Boehme" wrote:
> >
> > Raphael,
> >
> > "getAllowMaximize()" (and the corresponding maximization,
> for that matter)
> > does not have to do with a portlet being editable or not.
> > But apart from that I would agree that having an
> "Editable/Customizable/<any
> > other suggested name>" interface to derive from has its merits.
> >
> > Back to "getAllowMaximize()": is there still some
> enthusiasm about window
> > manager-style stuff included in a future Portlet API
> (something like along
> > the lines of event handling for maximize, minimize,
> restore, close, etc) ?
> >
>
> You're right. Customizable should not deal with the window
> manager like
> features but only with edition/customization properties.
>
> Is there any use for allowing the Portlet to specifically alter the
> maximize/minimize/close operations which never alter the portlet
> content itself ?
>
> I think most of the functionality can be achieved by using different
> controls (or by allowing parameters in the control markup) eg:
>
> <control name="EditableBoxControl">
> <parameter name="allowMax" value="no"/>
> <parameter name="allowMin" value="yes"/>
> </control>
>
> Any opinions on this ?
>
for such easy cases this is enough. But we have added a button "to
application",
which allows the call of a potential full-blown app behind the portlet. For
this
it's useful to send some additional informations about the current status
inside of the URL-call.
Additionally we have added for each portlet some special tags inside of the
registry, which are handling the related URLs:
<functions>
<function name="maximize">
<url>http://finance.yahoo.com</url>
</function>
</functions>
here one can specify which URL should be called if the button is pushed. The
current way to allways call the same URL for each portlet (OK, it's a
dynamic
one, but still...) is surely not enough. In the above approach you can
dynamically
e.g. call a configuration URL of the portlet. Another possibility is surely
to put these information into the "parameters" area of a portlet-entry.
Marcus
> --
> 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]
>
--
--------------------------------------------------------------
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]
