Browse Prior Art Database

Language and Context agnostic framework for Web UI Custom Actions

IP.com Disclosure Number: IPCOM000186566D
Original Publication Date: 2009-Aug-27
Included in the Prior Art Database: 2009-Aug-27
Document File: 3 page(s) / 69K

Publishing Venue

IBM

Abstract

Language and Context agnostic framework for Web UI Custom Actions, including configuration definitions, action lifecycle, API and framework processing engine

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

Page 1 of 3

Language and Context agnostic framework for Web UI Custom Actions

In a proprietary web UI it is sometimes desirable for the administrator of a system to be able to customize the interface to their companies own requirements. Current implementations allow the look and feel of the interface to be changed and some allow custom code to be inserted into the base Web UI.

    Current implementations are limited to a single implementation language and do not provide a language and context agnostic interface that can be used in a variety of programming languages.

    The invention is a language and context agnostic framework for web UI custom actions. It allows custom actions to be surfaced in several locations in a web UI and allows those actions to be implemented in a language agnostic fashion. The rendering of the custom actions inside the UI are context sensitive, i.e. they may appear as a button, link, menu item, navigation tree item, directory panl entry etc. based on where they are placed in a configuration file, but the implementation of the custom-action need not be coded for a specific context.

The invention provides a language and context agnostic framework for web UI custom actions consisting of:

  Web UI Configuration Definitions that define where the actions are to appear in the Web UI
Identical (as much as possible) frameworks for each supported language
A lifecycle for custom actions
Framework processing engine, which instantiates the custom actions and takes them through their lifecycle
Configuration Definitions
Possible places these could appear in the UI are as follows:
Detail View Definitions

As a custom button which appears after the system defined buttons on the same horizontal line.

As a property with a

element which will appear in the list of properties in the same order as in the definition.

Collection View Definition
As a button with a

element which will appear in the list of buttons in the same order as in the definition.

Menu Bar Definition

         As a top level or sub level menu item with a

element which will appear in the menu in the same order as in the definition. Navigation Tree Definition

As a top level or sub level node with a

element which will appear in the tree in the same order as in the definition.

Home Page Definition

         As a custom directory type entry which will appear in the directory panel in the same order as in the definition.
an example of one such definition, defining a custom action implemented in Java* would be:

Page 2 of 3

<

java-action-class>com.ibm.serviceregistry.customaction.examples.IncrementVersio

nNumbers</

bundleName

com.ibm.serviceregistry.customaction.examples.TerseResourceBund le

and an example of one such definition, defining a custom action implemented in Javascript would be:

<

js-action>

js-action>

Framework
The framework consists of:

A CustomActionContext object that is passed to eac...