Outline
| Table of Contents |
|---|
Component Overview
The PortletBrowser javascript component is a Fluid-based uPortal component designed to assist users in browsing their portlet registry. Examples of this component's use within uPortal include both the "add portlet" interface in the main user layout and the portlet listing table presented as the first screen in the Portlet Administration portlet.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
Component Options
Subcomponents
The PortletBrowser delegates functionality to a number of uPortal-specific subcomponents. These subcomponents include the PortletRegistry, as well as three view components. These three views create the user-visible interface associated with the component; the top-level component has no associated markup and its configuration does not include any selectors. The markup for all three views is expected to be contained within the container provided during the top-level component initialization.
CategoryListView
The CategoryListView component is intended to provide an interface for browsing category information and selecting/deselecting categories. In a typical implementation, the category list view will provide a list of categories, which once selected will update the portlet view with a list of members of the chosen category.
PortletListView
The PortletListView component is intended to provide an interface for browsing portlet information and selecting/deselecting portlets. Individual implementations may elect to provide an additional detail view for portlets or provide additional selection interactions.
SearchView
The SearchView component is intended to provide an interface for searching the portlet registry. Search requests will typically update the portlet view, and search queries may or may not be combined with the current category selection. A typical implementation of this view component consists of a simple search form, and such an implementation is provided as the default component.
Component State
The PortletBrowser maintains a "state" property map capable of tracking information about the user's browsing and searching operations. These properties are visible to subcomponents and may be accessed by them, but should not be directly updated by the subcomponents themselves. Write operations to the state map are generally expected to be performed via configured event listeners.
...