> 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.
Excellent idea.
> - I'd like to present portlets in several "panes" to avoid cluttering
> the screen with to many portlets.
How would you implement that?
> - 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.
Currently, I have three different versions of my portal which are
differentiated via query string. Right now, everything is done with if
statements and the ECS. I would love to be able to define the three default
screens by editing XML. This would really help make my project easier to
manage.
<snip>
> 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
> - or as multiple small XML files (as it is today)
> - defaultPortlets.xml -> anonymous access
> - <username>.xml -> authenticated access
> - allPortlets -> portlet registry
> - allProfiles -> profile registry
I would think you'd want multiple files. This is more organized and easier
to maintain for absolutely huge sites.
There should be some provision for storing those files in a db, though.
-ed
--
--------------------------------------------------------------
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]
