WebSphere Portal Server - Changing Portal Layout dynamically

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Portal Server > August 2006 > Changing Portal Layout dynamically





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Changing Portal Layout dynamically

2006-08-01, 1:29 pm

Hi,

Is it possible to change portal layout dynamically. For instance, when a user does a particular action is it possible to dynamically change the layout(make two portlets in the page disappear) and make the page align itself appropriately.

Appreciate any responses in this regard.

Thanks,
Sanjay.
Joydeep B

2006-08-01, 1:29 pm


You can maximize portlet 1 this will push out portlet 2 & 3

2006-08-01, 1:29 pm

This is not possible with WPS 5.0 / 5.1. However, you can have two portal pages. In one of these portal page, you keep all the portlets and in the 2nd page, you can remove some of these portlets. Then make your portal page 1 as the default page under My P
ortal. On a user event on page 1, you can call page 2 using the <wps:urlGeneration tag. Thus this functionality gets implemented.
j_kokil

2006-08-01, 5:59 pm

I also encounter little bit similar scenario.

I have to develop a portlet app.
In which Admin, Retailer and Distributer has a different look.

So should I develop 3 different portlet and based on who logs in hide other two portlet or I will use personalization.
But I belive personalization will support upto some extent. So does it help in this case while Admin, Retailer and Distributer pages sometimes look different but most of time they are similar.

2006-08-24, 1:30 am

You can try to do a "smart" theme to handle this situation or go cooperative portlets route. Both have draw backs.
Raymond Khalife

2006-08-25, 1:44 am

Hello,

We have a similar scenario: A search portlet, you search for stuff and when you click on an entry portlets appear on the right hand side with details about the entry.

What we did was create a custom 'NoSkin' skin. The search portlet has a standard skin applied, the detail portelts have our NoSkin skin applied. The skin doesn't render anything at all, if fact this is the code for it:

########################################
##############################
<%@ page session="false" buffer="none" %>
<%@ taglib uri="/WEB-INF/tld/portal.tld" prefix="wps" %>
<wps: constants/>
<wps: if portletState="Normal,Maximized,Solo">
<wps: portletRender>
<font color="red"><wps: problem bundle="nls.problem"/></font>
</wps: portletRender>
</wps: if>
########################################
##############################

The detail portlets are responsible for rendering their borders themselves. So they look for a selected entry in the session. If there is none, they will just render an empty page, and they just seem to be not there. If there is an object in the session t
hey seem to 'appear'.

Of course with this you loose the ability to change the skin of your portlet on the fly.

Cheers,
Raymond
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com