Browse Prior Art Database

System and Method for Designing Dynamic Layout Manipulation in Portal System

IP.com Disclosure Number: IPCOM000180506D
Original Publication Date: 2009-Mar-11
Included in the Prior Art Database: 2009-Mar-11
Document File: 6 page(s) / 79K

Publishing Venue

IBM

Abstract

Currently in a portal system, the integration is not well organized between server-side layout management mechanism and client-side technology based user experience: 1, for server-oriented layout solution, there’s a request for refreshing the entire page when submitting an update of the layout. This gives an impact on user experience. 2, for server-independent layout solution, there’s no communication between client and server. So the change made by client-side can not be uploaded to server, and the server can not have actions on client-side well managed. To provide a dynamic solution, we extract layout manipulation as a standalone part. So that we can make: 1, layout actions server-independent 2, layout access rights managed by server 3, layout profiles asynchronously updated

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 6

System and Method for Designing Dynamic Layout Manipulation in Portal System

Our solution:

The problem is solved by following steps:

1, extend layout framework by making it adaptable to more actions implemented by client-side technology;
2, build a new communication mechanism between client and server. So that actions on client side is manageable, and each change on layout made by client is updated to server dynamically and asynchronously.

In short, the actions' codes are provided to clientduring client's first request, and layout changes made by end user's actions are updated to server inan asynchronous manner.

Details:

This disclosure focuses on

        1, extension of layout framework,
2, architecture of portal after our solution applied.

From server side:

1, 2 repositories for layout data: Layout Access Control and Layout Profiles 2, a separate component: Layout Manager is introduced.

From a user's view:

1, a page is composed of several portlet windows, and layout actions are based on these windows;
2, there's no fixed style of layout framework any more. A portlet window has location parameters, so it can be dragged and dropped anywhere on the page. 3, consequently more actions can be defined, such as resizing, overlapping and etc. And all actions can be implemented server-independently.

The following figure is an example of a portal page's layout:

1

Page 2 of 6

2

[This page contains 1 picture or other non-text object]

Page 3 of 6

3

[This page contains 1 picture or other non-text object]

Page 4 of 6

Actions Codes:Implementation of Layout Actions: drag&drop, resize, etc.

Copy of Actions Codes: The codes copy to user's client, then end users can use the implementation to change portal page's layout. It's server-independent. Layout Access C...