Rapha�l Luta wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > 1.1
> >
> > -ability to set refresh rate within portlet markup
> >
> > -boolean property for user authentication
> >
> >
> > -add support for user profiles stored in a db with
> > additional support for saving some info in cookies and the
> > ability to configure this entirely in the properties file
> >
> > -add support for portlet state
> >
>
> I was thinking of improving the Portlet Site Markup, to address
> some of this issues. Some of my ideas are:
>
> - before implementing a full db backend for user preference storage
> why not use the markup to serialize the data in XML.
+1. The only time IMO we should serialize to JDBC/SQL is when it makes
sense. XML rocks for what we want this to do. I would rather serialize
it to a file. It makes much more sense.
> - I'd like to present portlets in several "panes" to avoid cluttering
> the screen with to many portlets.
+1. So would I
> - 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...
<skin/><!-- special skinning for this pane -->
> <portlet>
> <classname/>
> <url/>
> <metainfo/>
> <parameter/>
> </portlet>
> <portlet/>
> <portlet/>
> </pane>
> </portlets>
>
> <!-- 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.
> <profileregistry>
> <profile name="ComputerGeek">
> <description>Selection of channels of interest for
> computer geeks</description>
> <pane name="Personal Computers"/>
> <pane name="Web"/>
> <pane name="Hacking"/>
> </profile>
> <profile name="BusinessGuy"/>
> </profileregistry>
> <portletregistry>
> // basically the content of allPortlets, allow the user
> // to chose new portlets
> </portletregistry>
> </portal>
>
> This can be implemented :
> - either as a single large XML file (<=> database), this
> will ease configuration but will be a bit harder to implement because of
> increased serialization costs
Not really. It is really only written to in rare circumstances.
Slashdot only gets about 250 additions a day that would have to be
written to disk.
> - or as multiple small XML files (as it is today)
> - defaultPortlets.xml -> anonymous access
> - <username>.xml -> authenticated access
> - allPortlets -> portlet registry
> - allProfiles -> profile registry
Yes. This should be worked out mroe. I agree.
> 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.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please 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]
