"Kevin A. Burton" wrote:
>
> > - I think it would be useful to create "portal profiles" so that newly
> > registered users can access different pre-configured setup before
> > having to customize their own space.
> >
> > Example markup:
> >
> > <portal>
> > <!-- Portlets Definition for anonymous connections -->
> > <portlets>
> > <skin>
> > <!-- general skin hints for all panes
> > ex: should I show Pane name ?
> > how can I switch pane ?
> > ...
> > -->
> > </skin>
> > <!-- visible pane when first connecting -->
> > <defaultpane>Home Page</defaultpane>
> > <pane name="Home Page">
>
> I would rather specify an HREF for portlets here...
>
Yes, but there should still be the possibility to override parameters
and meta-info locally, ie:
<portlet href="portlets:FilePortlet">
<url>myfile</url>
<metainfo>
<title>MyTitle</title>
</metainfo>
</portlet>
in the portlets registry:
<portlet name="FilePortlet">
<classname>org.apache.jetspeed.portlets.FilePortlet</classname>
<url>defaultFiletoBeincluded</url>
<metainfo>
<title>DefaultTitle</title>
</metainfo>
</portlet>
> > <!-- Portlets Definition for logged-in user luta -->
> > <portlets user="luta">
> > <skin/><!-- Skin preference for user -->
> > <defaultpane>Corporate</defaultpane>
> > <pane name="Corporate">
> > <skin/>
> > <portlet>
> > <state>NORMAL</state>
> > <classname/>
> > <url/>
> > <metainfo/>
> > <parameter/>
> > </portlet>
> > </pane>
> > <pane name="Internet"/>
> > <pane name="Personal"/>
> > </portlets>
>
> Personal profiles (as opposed to the default profile) should probably be
> obtained by PortletFactory.getInstance( User ) instead of being in the
> main XML file.
>
+1. The model works better when storing each portlets section in its own file
>
> > Not addressed by this markup:
> > How do we allow portlet designers specify configuration options ?
> > For example RSSPortlet (or PortletControl) should allow (at least)
> > 2 configurations parameters:
> > - display description if available ?
> > - how many items to display ?
>
> I was thinking that each portlet could have a control panel UI... but I
> am not satisfied with that solution.
>
I was more thinking of a cross between JavaBeans and EJB:
- each Portlet who wish to handle complex parameters should declare a
Customizable interface and implement its complete GUI panel
- those who only handle simple configuration items should declare them
as such in the portlet registry and implement only getter and setter
methods, the Jetspeed engine creating the default GUI from the properties
descriptor.
Example of property descriptors:
<portlet name="RSSPortlet">
<classname/>
<url/>
<metainfo/>
<parameter/>
<properties>
<property name="displayItem">
<type>Integer</type>
<default>5</default>
<description xml:lang="en">Number of items
to be displayed</description>
</property>
<property name="displayDescription">
<type>Boolean</type>
<default>false</default>
<description xml:lang="en">Display the items
description when available ?</description>
</property>
</properties>
</portlet>
Does that makes sense to you ?
--
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://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
