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) ?
Cheers,
Thomas Boehme
----- Original Message -----
From: "Raphael Luta" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Friday, November 10, 2000 14:20
Subject: Re: editable portlets for release 1.2
Stephan Hesmer wrote:
>
> Hi,
>
> I would like to introduce me here. I'm working with Ingo and Thomas at
> Jetspeed and work since 4 weeks with Jetspeed. There are a lot activities
> and todos at Jetspeed at the moment - and you can count on me! Your plan
to
> release version 1.2 in the near future (ASAP) and to design a completely
new
> Jetspeed 2 are very good. Especially the the Portlet API.
>
> I have some issues for the release 1.2:
>
> - how about a real edit function for new and existing portlets? The
current
> functionality is just an info screen. I would suggest to add something
like
> a getAllowInfo into the Portlet Interface. So the existing portlets can
> still show their InfoScreen and new portlets can implement a real edit
> function.
> comments?
>
I'd rather remove getAllowEdit() and getAllowMaximize from the
main Portlet API and define a new Customizable interface:
interface Customizable {
getAllowEdit();
getAllowMaximize();
getCustomizer(); //or whatever is required
}
Such an interface would allow easy identification of Customizable
elements in the system.
> - there are still bugs in Jetspeed. The Rundata data is not passed to
every
> function (I'm speaking here of getAllowEdit). One other thing is, that in
> PortletConfig still exist some request sensitive data. I could post more
> detailed information, if desired.
>
There's definitely a life cycle issue there, say my response to Thomas.
--
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]
