On Tue, 16 May 2000, Kevin A. Burton wrote:
> Jeff Prickett wrote:
> >
>
> Sweet!
>
> Now here is a larger issue? Should this become a standard or optional
> portion. Some people haven't liked the fact that Jetspeed would require
> a database. Of course if they aren't cutting code they don't get that
> big of a vote :)
>
> I am all for seeing this as a standard portion of Jetspeed, that is
> iCalendar and having the database as a requirement.
>
For this release, I think the Calendar can be optional, but I would like
to see it become a core piece of Jetspeed.
I prefer, it to be, an "optional" part of the core. What I mean by that is
that any calendar initialization failure should not preclude the loading
of the main portal screen or any non-calendar functionality.
So it should be in the Core part of Jetspeed, but shouldnt unecessarily
cause configuration trouble with other modules.
Make sense. Seems a little contradictory, but I hope you know what I mean.
> Also, should iCalendar be a Portlet or an Application? Hmmm?
Right now its going to consist of a couple of turbine screens, so its more
separate from a portlet.
I would, however, like to see it become a Portlet in future versions
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]
