Manjuka Soysa wrote:
> Hi all,
> I am interested in developing some standard applications/portlets for Jetspeed:
> - email browser
One of my top choices. Don't know of any OS project in java and/or xml
There are good javax.mail implementation (good part of the backend). It
should not be difficult to write a set of portlets wrapping one of these
implementations. I remember one of the early releases of javax.mail had
a functional servlet to read mail. It was just a proof of concept, but
the API gives a very good access to messages, parts, attachments. I
think somebody is writing/has written a tool to deliver mail messages as
XML files. If this is true, this XML format could be XSLTransformed into
a RSS channel (for the folder and message list views), and have a URL
that would deliver the message as a separate portlet when clicked.
>
> - to do list
iCalendar has a VTodo object. This is a blessed standard for handling
these objects.
An enhanced Jetspeed Content channel could support most of the display
functionality. (Showing, adding lists of items in categories with
descriptions). We would need to have dates (when tasks are due), state
(done,assigned,...).
>
> - problem / work assigment and tracking
I think Scarab
http://scarab.tigris.org/index.html
is targetted similarly. It is a Turbine app, but it would not be
difficult to wrap its screens into portlets once the new portlet API is
implemented. Jon knows more about current status.
>
> - time sheet entry
You mean for project time assignment?
>
> - calendar (I heard this is being done)
There is already available the vCalendar Object Model. Work is needed
there. In fact, todos are a part of the vCalendar standard. Look at the
list for a recent report on status of these module. Most of the display
(different views, events, forms, ...) and parts of the object model are
missing.
>
> I'd like to find out if
> a) Anyone else is already doing these apps
> b) Anyone else is interested
> c) With the new layout system and portlet API being developed, is jetspeed to
>volatile to develop these now
What could be done is:
Publish a functional spec of your choice app (different views, flow of
control, ...) Test if this view can be mapped into our new proposed API,
and use it as a blackboard to discuss Portal API issues, spec, design or
implementation problems, etc. This would enhance both the portlet api
and the spec of the app.
Proceed designing (or integrating from other projects) modules that
implement the backend parts (object model, functions like retrieval for
email, calendar objects, ...)
Meet when we have a decent implementation of a portlet engine (with fine
level security) and drink some beers :-)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
