Browse Prior Art Database

Hierarchical Portlet Manager Disclosure Number: IPCOM000031527D
Original Publication Date: 2004-Sep-28
Included in the Prior Art Database: 2004-Sep-28
Document File: 2 page(s) / 36K

Publishing Venue



The core idea of this invention is to provide a portlet manager for high-level portlet control. It would handle all the portlets, and their potential hierarchical relationships, on a panel or page. Other UI managers today, such as for example Windows Task Manager, show task status and give control per window. It also doesn't handle hierarchical relationships among sub-window-level UIs (e.g., portlets). A hierarchical portlet manager would be a manager (viewer and controller) at the sub-page level, as well as hierarchical, distinguishing it from other UI managers today.

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 79% of the total text.

Page 1 of 2

Hierarchical Portlet Manager

Portlet-based UIs are quickly becoming very pervasive for web sites as well as web-based admin consoles, most notably supported by IBM's ISC (Integrated Solution Console). A potential problem is that as we're shifting the UI paradigm from full page-based content areas to smaller sub-page portlet-based content areas, the corresponding indicators and controls for handling the relationships among related portlets is not being provided to users.

Window managers of today do not handle subsets of the window or page (e.g., tiles, frames, or portlets). However, there is a strong emerging need today for such high-level portlet management. High-level portlet management would include such things as a capability to act upon more than one portlet at a time (e.g., closing or printing a string of hierarchically related portlets, etc.).

A portlet manager could show the relationship of all portlets on a workpage and allow the user to do high-level actions such as to minimize, expand, or close sets of portlets. This is shown below in Figure 1. Note how the base highest-level portlets ("Data Collection Tasks" and "Thresholds") do not have close buttons. They cannot be entirely closed - just minimized. But, the sub-portlets of "Thresholds" can be minimized as well as closed.

Figure 1 - Basic Hierarchical Portlet Manager

There are possible extensions to this base idea. One is to add capability to close all or minimize all sub portlets. This is shown in Fi...