Yes... Jetspeed 1.0 is still being worked on. :) But here are some
ideas I had
over the last couple of days for 1.1.
Thoughts?
------------------------------------------------------------------------------
- Improve RSS support. Only use 1 stylesheet this should be *very*
smart and
work across RSS 0.90, 0.91, and 0.92.
- Support the ability for portlets to do their own posts. Each portlet
needs
to define it's own namespace. If they don't define their own
namespace then
two portlets might conflict and one might accidentally realize it was
posted.
also might want to thing about a service() method of a portlet.
- require all portlets to use XHTML. Then we can process the <form>
data
and add namespaces within the Factory and pull them out when we call
service() on a Portlet
- PortletMarkup
- ability to have colums that only have a certain number of portlets
- Portlets provide layout hints which the Portlet controller is
supposed
to pay attention to.
<portlets>
<!--
Provide a remote url that has skin data. This would be the
default but would be removed if the user has his own skin.
-->
<skin href=""/>
<portlet>
<metainfo>
<!-- Only a suggestion to the PortletController -->
<!-- Provide a suggestion that the PortletController
should include a title -->
<layout title="false" columnId="0" rowId="0"
state="minimized"/>
</metainfo>
<portlet/>
</portlets>
<skin>
<!--
Define what columns to have and their widths.
-->
<column id="0" width="40"/>
<column id="1" width="100%"/>
<column id="2" width="40"/>
<page-title-background></page-title-background>
<page-title-foreground></page-title-foreground>
<portlet-title-background></portlet-title-background>
<portlet-title-foreground></portlet-title-foreground>
<portlet-body-background></portlet-body-background>
<portlet-body-foreground></portlet-body-foreground>
</skin>
- Add support for a Portlet "state"
Include the state in the cache engine so that different cache states
are
correctly displayed.
this.getPortletConfig().getState()
- STATE_NORMAL
- STATE_MINIMIZED
- STATE_MAXIMIZED
This is necessary so that portlets can determine how much
information
to display when the user changes their state. For example a
maximized
portlet might display extra graphics, etc.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
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]
