Neeme Praks wrote:
>
> > -----Original Message-----
> > From: Demo User [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, June 08, 2000 1:15 AM
> >
> > What is the "customization file" for?
>
> My current implementation uses "psml" parameter from request to
> determine the "customization file". The file is just a specification of
> portlets, like current default.psml or turbine.psml.
>
I think Kevin question was what is the purpose of these customization files ?
What is your need that's not currently fullfilled by the 1 customization/user
approach currently used ?
The next question will be: is this need general enough to implement it in the
core jetspeed, as an add-on or should it stay a local patch made in your
installation.
> > BTW if you just did this so that
> > the user can have more than one "page" or "screen" of
> > portlets, this can be done with the PanedPortletController.
>
> Actually, I don't understand PanedPortletController, so I didn't
> consider this.
> As there is no docs about this, can someone explain me the concept
> behind this approach?
> First of all, what/how is PanedPortletController used? What does it do?
> And how could this kind of customization be achieved with
> PanedPortletController?
>
First, PanedPortletController doesn't exist anymore, its functionality is now split
in the CardPortletController and the PanedPortletControl.
The controller function is very similar to the card layout manager in AWT, it
organises the children elements of the portlets it manages in a stack and only
display one element at a time
For example, with this PSML:
<portlets>
<controller
name="org.apache.jetspeed.portal.controllers.CardPortletController">
<parameter name="parameter" value="pane"/>
</controller>
<control name="org.apache.jetspeed.portal.controls.PanedPortletControl"/>
<portlets>
<layout position="0"/>
<entry/>
</portlets>
<portlets>
<layout position="2"/>
<entry/>
</portlets>
<portlets>
<layout position="1"/>
<entry/>
</portlets>
</portlets>
When you first access the file only the entries in the <portlets> at position 0
will be displayed on screen, to access the <portlets> elements you need to specify
which position to display with the pane parameter. For example:
http://host/servlet/jetspeed/pane/1/
to select the <portlets> at position 1, etc...
If you specify a PanedControl with the CardController, the Control will display
"tabs" above the display area of the portlets with links to the various <portlets>
elements, displaying their titles in the links.
If you don't specify any control, the user will have no idea that you have
other cards available and it's up to you to provide the links to the other cards.
Basically, the CardController allows you to describe several pages while keeping the
same Turbine screen and nivigations elements.
> Anyway, I don't like the idea of putting all the "pages" in one psml
> file because this can get really big and the whole file has to be parsed
> on each request. Am I correct here?
>
> Thanks,
> Neeme
>
You are right, you will experience some performance degration if you use *really*
big PSML files, but then you're probably designing a full website and not necessarily
a portal and you should not use Jetspeed alone for creating a full blown site.
You have other options to achieve the feature though :
the one I would be using is to implement as many turbine screens as you have
different pages to display (based on the Home screen model) and instead of
using
PortletFactory.getInstance(User)
and let the factory decide where to look for the psml file, use
PortletFactory.getInstance(url)
and give the factory the exact location where you want to look for your file.
This way you can implement whatever are your requirements are without modifying
the basic functionality and worry about backward compability.
[if a brave soul wants to copy this and start a user documentation,
I would be most grateful]
--
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]
