Rapha�l Luta wrote:
>
> "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:
+1.
Did you want to write an XMLSchema for this? I was thinking that 1.2
needs 2 things.
- Jetspeed Portal Structure Language
- Jetspeed Portal Content Language
The later I already have but just haven't commited yet. It should allow
Slashdot style content and is very similar to RSS 0.91 so people
shouldn't have a problem with it.
The schema will allow us to build the API from castor.
<snip>
> >
>
> +1. The model works better when storing each portlets section in its own file
This way you could have a set of portlets but then change the skin in
runtime. That would be *really* cool.
> >
> > > 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
I was thinking about something like this. After a while I started to
think that this wasn't clean for a web app. I would be more interested
in it providing a URL.
I am working on a simple bean that when you point it at an XMLSchema
will create a nice UI for instantiating an XML document from the
schema. This should provide all the customizablity we need :)
Cool idea to type the properties. This will be put on the TODO list
which is growing more than it is shrinking :(
<snip>
--
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]
