On Thu, 9 Nov 2000, Raphael Luta wrote:
> I propose that the work on Jetspeed is organised in the following
> fashion.
>
<snip>
> * In parallel to this, start working on a brand new Jetspeed 2
> design along with a generic Portlet API.
>
OK I like where this is going. We need to look at "requirements" or
our wish list so to speak.
IMHO BEFORE we even begin having discussion on the API we define what
we want a portlet to do.
When I first started with Jetspeed I read up on "portlets". I read
something on Oracles site about their vision of portlets as a way of
docking content into the browser favorites bar just under the URL location
bar.
I am not sure technically how this is done.
Secondly, I believe that user customization should be a top priority in
Jetspeed.
> * As soon as the Portlet API is solidified, start a back-port of
> this API to the 1.2 branch, thus creating a new 1.x Portlet API
> implementation.
>
OK, let me see if I follow you here. We create a brand new implementation
that implements both 1.2 api and the 2.0 api to act as a bridge for
current applications who are coding to Jetspeed.
I think that this is fine as long as we dont limit our 2.0 api based on
how well it back-ports. If the new API doesnt backport I would be in favor
of dropping support for the 1.2 api.
My status as far as Jetspeed goes is that I might be able to spare a few
hours a week for design discussions. Beyond that I cant help much more at
this point because of my commitment to the iCalendar code.
I have been pretty quiet on the lists as I have been buried under work :(.
Jeff Prickett
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
