MENU LAUNCHING STRUCTURE
FIELD OF THE INVENTION
[01] This invention relates to menu structures, and in particular actions to be
taken upon selection of a menu item.
BACKGROUNDOF THE INVENTION
[02] When an item is selected from a menu, an action associated with the
menu item is launched directly. This does not take advantage of functions
common to several items in the menu. This also fails to take into account the
current state of the system.
[03] A structure for defining a menu would preferably associate numerous
variables with the menu items, and selection of a menu item would execute any
of various functions, some of which may be common subsystems, depending on
the variables associated with the menu items.
SUMMARY OF THE INVENTION
[04] According to one aspect, the invention provides a method of responding
to selection of a menu item. A launch type of the menu item is determined, the
launch type being associated with the menu item in a definition of the menu
item. If the launch type indicates that a list is to be presented, a list subsystem is
invoked and the value of a parameter associated with the menu item in the
definition of the menu item is passed as an input to the list subsystem. If the
launch type indicates that a form is to be presented, a form subsystem is
invoked and the value of the parameter is passed as an input to the form
subsystem. If the launch type indicates that a custom action is to be performed,
a custom action defined by the value of the parameter is invoked.
1
[05] According to another aspect, the invention provides a method of
defining a menu. For each of a plurality of menu items, a value of a label is
stored in association with the menu item. For each of the plurality of menu
items, a value of a launch type is stored in association with the menu item. For
each of the plurality of menu items, a value of a parameter is stored in
association with the menu item.
[06] The methods of the invention may be stored as processing instructions
on computer-readable storage media, the instructions being executable by a
computer processor.
[07] The invention allows different actions to be performed on selected menu
items, depending on a launch type of the item included in the definition of the
menu item. The structure of the definition of the menu items also stores a
parameter for use when performing the defined action type. For some launch
types, the parameter is an input to a common subsystem. For other launch
types, the parameter is a class name of an object, with a specific action defined
for the object.
BRIEF DESCRIPTION OF THE DRAWINGS
[08] The features and advantages of the invention will become more apparent
from the following detailed description of the preferred embodiment(s) with
reference to the attached figures, wherein:
FIG. 1 is a diagram of an example menu definition according to one
embodiment of the invention; and
FIG. 2 is a flowchart of a method executed upon selection of a menu end
item according to one embodiment of the invention.
[09] It is noted that in the attached figures, like features bear similar labels.
2
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[10] Referring to FIG. 1, a diagram of an example menu definition according
to one embodiment of the invention is shown. FIG. 1 shows the contents of an
XML file in which a menu is defined. The example menu shown in FIG. 1 has
several layers, selection of menu items in some layers (for example, the menu
item labeled "Equipment") making submenus accessible to a user. Ultimately
end menu items are presented, selection of which performs some task other
than opening a submenu. The menu shown in FIG. 1 contains three menu end
items, each indicated by a value of a label variable named "label". The three
menu end items in the menu and available for selection by a user are "Chassis",
"Card", and "Power Supply". Each menu end item also has a launch type
variable named "launchtype". The value of the "launchtype" variable for the
"Chassis" menu item is "action". The value of the "launchtype" variable for the
"Card" menu item is "list". The value of the "launchtype" variable for the
"Power Supply" menu item is "form". Each menu item also has a parameter
variable named "className". The value of the "className" variable for the
"Chassis" menu item is "example.action.ChassisAction". The value of the
"className" variable for the "Card" menu item is "example.equipment.Card".
The value of the "className" variable for the "Power Supply" menu item is
"example.equipment.PowerSupply".
[11] The menu described with reference to FIG. 1 is an example only. In
general, the menu will be defined to have a structure in which each end item
has associated with it at least three variables, one of the variables being a label,
one of the variables being a launch type, and one of the variables being a
parameter used in executing an action.
[12] Referring to FIG. 2, a flowchart of a method executed upon selection of a
menu end item according to one embodiment of the invention is shown. The
method starts when a menu end item is selected 50 from a menu. At step 52 it is
determined whether the value of the variable "launchtype" of the selected item
3
is equal to "action". If so, then a code module is executed at step 54. The code
module is within an object whose class and name is derived from the value of
the variable "className". The name of the code module is pre-defined and
therefore known upon selection of the menu item. The logic within the code
module can perform any defined task. For example, the code can consult the
current state of the system, determine the information currently defined for the
entity represented by the selected menu item (as determined from the value of
"className"), and launch either a list or a form depending on whether the
entity currently needs further configuration.
[13] If the value of the variable "launchtype" of the selected item is not equal
to "action", then at step 56 it is determined whether the value of the variable
"launchtype" of the selected item is equal to "list". If so, then at step 58 a list
subsystem is invoked, using the value of "className" as an input to the list
subsystem. The list subsystem determines the specific type of List window to
open using the value of "className". Using the value of "className", the list
subsystem determines the type of entity selected and determines the format of
the list. The format of the list is pre-defined within the list subsystem for all
entity types, along with information about performing searches for the type of
entity indicated by the value of "className". The format is preferably stored as
a text file in XML format which describes the layout of the contents of the List
window. The information contained in the list subsystem includes data to be
displayed as well as filters to be applied. Using the value of "className", the
list subsystem also determines the specific entity referred to by the selected
menu item, both the entity type and specific entity derivable from the value of
"className". The list subsystem opens a List window, preferably directly into
the display manager for the application from which the menu was accessed,
and populates the List window with current data for the specific entity.
[14] If the value of the variable "launchtype" of the selected item is not equal
to "list", then at step 60 it is determined whether the value of the variable
4
"launchtype" of the selected item is equal to "form". If so, then at step 62 a
form subsystem is invoked, using the value of "className" as an input to the
form subsystem. The form subsystem determines the specific type of Form
window to open using the value of "className". Using the value of
"className", the form subsystem determines the type of entity selected and
determines the format of the form. The format of the form is pre-defined within
the form subsystem for all entity types. The format is preferably stored as a text
file in XML format which describes the layout of the contents of the Form
window. Using the value of "className", the form subsystem also determines
the specific entity referred to by the selected menu item, both the entity type
and specific entity derivable from the value of "className". The form
subsystem opens a Form window, preferably directly into the display manager
for the application from which the menu was accessed.
[15] If the value of the variable "launchtype" of the selected item is not equal
to "form", then the variable "launchtype" has an unrecognized value and an
error occurs at step 64. Ideally this should not happen because when the
method described with reference to FIG. 2 is compiled the unrecognized value
of the "launchtype" variable will be detected. However, an error may be
processed at step 64 for completeness or as a safeguard. The actions to be taken
upon occurrence of the error are not within the scope of this application, but
may be simply presentation of an error message.
[16] As an alternative, other launch types and their associated actions can be
defined and included in the menu definition. The use of the value of the
variable "className" will depend on the logic performed for the launch type.
A graph launch type and subsystem, a map launch type and subsystem, and a
tree launch type and subsystem are examples. In the example of a graph launch
type, for example, the method described above with reference to FIG. 2 can be
modified so that it is determined whether the value of "launchtype" is equal to
5
"graph". If so, then a graph subsystem is invoked using the value of
"className" as an input parameter.
[17] Broadly, when a menu item is selected, the launch type defined for the
menu item is determined, and an action taken based on the launch type. If the
launch type indicates that a custom action is to be performed, then a parameter
defined for that menu item is used to invoke the custom action. If the launch
type indicates that a list is to be displayed for the menu item, then a list
subsystem is invoked using the parameter defined for that menu item as an
input. If the launch type indicates that a form is to be displayed for the menu
item, then a form subsystem is invoked using the parameter defined for that
menu item as an input. Other launch types and their associated actions may
also be defined.
[18] The logic of the methods is preferably in the form of software, and may
be stored as instructions on computer-readable storage media which can cause a
computer processor to act upon selection of a menu end item. The definition of
a menu, including associations of labels, launch types, and parameters for menu
items, may be stored on computer-readable storage media which can cause a
computer processor to present a menu.
[19] The embodiments presented are exemplary only and persons skilled in
the art would appreciate that variations to the embodiments described above
may be made without departing from the spirit of the invention. For example,
the menu may be defined using other means than an XML file. As another
example, the order in which the value of the "launchtype" variable is
determined may be varied, and the method may be any method which is
logically equivalent to that described above with reference to FIG. 2. Other
values of the "launchtype" variable can be used. The scope of the invention is
solely defined by the appended claims.
6
I/W CLAIM:
1. A method of responding to selection of a menu item, comprising:
determining a launch type of the menu item, the launch type associated
with the menu item in a definition of the menu item;
if the launch type indicates that a list is to be presented, invoking a list
subsystem and passing the value of a parameter associated with the menu item
in the definition of the menu item as an input to the list subsystem;
if the launch type indicates that a form is to be presented, invoking a
form subsystem and passing the value of the parameter as an input to the form
subsystem; and
if the launch type indicates that a custom action is to be performed,
invoking a custom action defined by the value of the parameter.
2. The method of claim 1 wherein the list subsystem determines a format of
the list from the parameter, and wherein the form subsystem determines a
format of the form from the parameter.
3. The method of claim 1 further comprising invoking a different subsystem
and passing the value of the parameter as an input to the different subsystem if
the launch type indicates that the different subsystem is to be invoked.
4. The method of claim 3 wherein the launch type indicates that a graph
subsystem is to be invoked.
5. The method of claim 3 wherein the launch type indicates that a map
subsystem is to be invoked.
6. The method of claim 3 wherein the launch type indicates that a tree
subsystem is to be invoked.
7
7. The method of claim 1 wherein the definition of the menu item is stored
in an XML file.
8. A method of defining a menu, comprising:
for each of a plurality of menu items, storing a value of a label in
association with the menu item;
for each of the plurality of menu items, storing a value of a launch type in
association with the menu item; and
for each of the plurality of menu items, storing a value of a parameter in
association with the menu item.
8

A . CLASSIFICATION OF SUBJECT MATTER
INV. G06F9/44 G06F3/048
ADD.
According to International Patent Classification (IPC) or to both national classification and IPC
B. FIELDS SEARCHED
Minimum documentation searched (classification system followed by classification symbols)
G06F
Documentation searched other than minimum documentation to the extent that such documents are included in the fields searched
Electronic data base consulted during the international search (name of data base and, where practical, search terms used)
EPO-Internal
C. DOCUMENTS CONSIDERED TO BE RELEVANT
Category* Citation of document, with indication, where appropriate, of the relevant passages Relevant to claim No.
US 2004/046804 Al (CHANG PETER H [US] ) 1-8
11 March 2004 (2004-03-11)
paragraph [0035] - paragraph [0059]
US 2003/098891 Al (M0LANDER MARK E [US] ) 1-8
29 May 2003 (2003-05-29)
paragraph [0027] - paragraph [0041]
□ Further documents are listed in the continuation of Box C. See patent family annex.
* Special categories of cited documents :
"T" later document published after the international filing date
or priority date and not in conflict with the application but
"A" document defining the general state of the art which is not cited to understand the principle o r theory underlying the
considered to be of particular relevance invention
"E" earlier document but published on or after the international "X" document of particular relevance; the claimed invention
filing date cannot be considered novel or cannot be considered to
"L" documentwhich may throw doubts on priority claim(s) or involve an inventive step when the document is taken alone
which is cited to establish the publication date of another "Y" document of particular relevance; the claimed invention
citation or other special reason (as specified) cannot be considered to involve an inventive step when the
"O" document referring to an oral disclosure, use, exhibition or document is combined with one or more other such docu¬
other means ments, such combination being obvious to a person skilled
"P" document published prior to the international filing date but in the art.
later than the priority date claimed "&" document member of the same patent family
Date of the actual completion of the international search Date of mailing of the international search report
8 June 2011 20/06/2011
Name and mailing address of the ISA/ Authorized officer
European Patent Office, P.B. 5818 Patentlaan 2
NL - 2280 HV Rijswijk
Tel. (+31-70) 340-2040,
Fax: (+31-70) 340-3016 Kusni erczak, Pawel
Patent document Publication Patent family Publication
cited in search report date member(s) date
US 2004046804 A l 11-03-2004 NONE
US 2003098891 A l 29-05-2003 NONE