> -----Original Message-----
> From: Rapha�l Luta [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 08, 2000 3:43 PM
>
> 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.
After reading your post, I understood that there is actually no need for
this. So let's just forget about it... Or if someone wants, he can do it
as a local patch.
> First, PanedPortletController doesn't exist anymore, its
> functionality is now split
> in the CardPortletController and the PanedPortletControl.
ok.
> 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.
cool. This is almost exactly what I need.
And I was kind of expecting for something like this, after being told
more than once that this is possible already ;-)
Just one question about the userconf files: does this position attribute
have to be a number or could it also be a simple string. I would prefer
to have names instead of numbers (then I could do a URL rewrite, to make
the URLs look friendly to outside world also). And, in what order are
the portlets displayed? In this numerical order or in the order they
appear in the file? I would prefer to have something like this:
<portlets name="myPage">
<entry/>
</portlets>
So I can reference the set with a normal name and all the portlets would
be displayed in the order they appear in the file. Makes easier to
change the order of portlets, right now I have to change all the
following portlet numbers...
> 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.
OK, probably the files won't get that big and it is not an issue. And
the filesize could be minimized also through the use of "inheritance"
(see my other post), so no duplicate information would be stored in the
userconf files.
> 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.
ok, thanks.
> [if a brave soul wants to copy this and start a user documentation,
> I would be most grateful]
Currently I don't have time for this... but if nobody does it by
september, I'll need to do it ;-)
Neeme
--
--------------------------------------------------------------
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]
