Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

METHOD AND PROCESS FOR MANAGING LARGER GUI PANELS ON SMALLER PERVASIVE DEVICES

IP.com Disclosure Number: IPCOM000014415D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 43K

Publishing Venue

IBM

Related People

David Lection: AUTHOR [+2]

Abstract

Most Graphical user interfaces (GUI's) designed today are designed for either 640x480 or larger screen size. Moving a GUI to a smaller screen size presents problems of scaling resolution, and loss of precision or intent. This method of grouping screen elements in a GUI results in better ordering and grouping on smaller screen sizes. The invention uses a grouping metaphor for related data in the GUI definition. In the preferred embodiment the GUI is coded in XML using the data group tag as follows:

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 63% of the total text.

Page 1 of 2

  METHOD AND PROCESS FOR MANAGING LARGER GUI PANELS ON SMALLER PERVASIVE DEVICES

    Most Graphical user interfaces (GUI's) designed today are designed for either 640x480 or larger screen size. Moving a GUI to a smaller screen size presents problems of scaling resolution, and loss of precision or intent. This method of grouping screen elements in a GUI results in better ordering and grouping on smaller screen sizes.

The invention uses a grouping metaphor for related data in the GUI definition. In the preferred embodiment the GUI is coded in XML using the data group tag as follows:

<DATA-GROUP NAME="dg-name">

</DATA-GROUP>

Within the data group other sub groups of data may be grouped using a group tag:

<GROUP NAME="group-name" ORDER="step-n">

</GROUP

Finally elementary data items may be added to the data group or any contained group. These are coded using the following data declarations: <STRING NAME="string-name" ORDER="step-n"> Hello, I am a string </STRING> <NUMBER NAME="number-name" ORDER="step-n"> 3.1419

</NUMBER>

<BOOLEAN NAME="name-of-boolean" ORDER="step-n"> TRUE </BOOLEAN> <LABEL NAME="name-of-label" ORDER="step-n"> I am a label </LABEL>

This is not an exhaustive list of all elementary data items defined, but enough elementary types to demonstrate the idea presented. The rendering engine reads and parses the data group's XML. During the parsing operation the rendering engine determines the number of logical groups of related data. A group of related data may be as small as a single data item, or a group, or the entire data group depending on the number of data fields. The rendering process then forms the logical groups of data into an input progression list. This list represents an optimal directed flow of input from the user. This order is affected by the specification of an order attribute on any group or elementary item. These order numbers allow the programmer of the XML to influence the general order of entry of data into the user interface. Any items that have and ORDER value of "1" will be processed first. Higher number order groups or elementary items will be processed before lower order number groups or items. If a group contains an item or items with an order, then the group will be considered to be of the order of the lowest contained ordered item. When all ordered items have been

1

Page 2 of 2

assembled, un ordered items will then be added to the list. The renderer then creates a user interface panel for each logical group in the list. If a logical group is to large for the target device then the group itself will be broken down into a series of sub panels, presented to the user sequentially, applying the same order process described above. The renderer adds to each user interface panel a cancel button, if the user interface in cancel-able. The renderer also adds small arrow icons to each page of the user interface. The icons when click allow the user to navigate back to previously completed pages to check previous d...