Method for seamlessly crossing GUI toolkit boundaries
First Claim
1. A computer-implemented process of executable computer code, comprising:
- providing, in a computer, a graphical user interface container object in a first graphical user interface toolkit, wherein the graphical user interface container object is incapable of recognizing containment relationships between the graphical user interface container object and any component objects from a second graphical user interface toolkit;
generating, in the computer, a graphical user interface component object in the second graphical user interface toolkit;
causing the graphical user interface component object to become contained by the graphical user interface container object; and
recording, in the computer, a containment relationship between the graphical user interface container object and the graphical user interface component object in a table that is external to the graphical user interface container object and the graphical user interface component object, wherein the table contains a plurality of entries, wherein each entry contains an identification of a container and an identification of a component, wherein the table defines a mapping between a plurality of components and a plurality of containers, wherein the first graphical user interface toolkit and the second graphical user interface toolkit define classes in an object-oriented programming language, and wherein the first graphical user interface toolkit is Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT) and the second graphical user interface toolkit is the other of Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT).
1 Assignment
0 Petitions
Accused Products
Abstract
A method, computer program product, and data processing system for facilitating the traversal of a hierarchy of GUI components containing components and/or containers from disparate GUI toolkits is disclosed. In a preferred embodiment, auxiliary associative data structures relating parent components in one toolkit to children in another toolkit are defined. When examining a component to determine if it has children, an appropriate associative data structure is consulted to determine if that component has a child from a disparate toolkit. In accordance with this preferred embodiment, additional associative data structures are defined, which also record the reverse “child-parent” relationship, so as to allow the GUI component tree to be traversed in both directions.
16 Citations
16 Claims
-
1. A computer-implemented process of executable computer code, comprising:
-
providing, in a computer, a graphical user interface container object in a first graphical user interface toolkit, wherein the graphical user interface container object is incapable of recognizing containment relationships between the graphical user interface container object and any component objects from a second graphical user interface toolkit; generating, in the computer, a graphical user interface component object in the second graphical user interface toolkit; causing the graphical user interface component object to become contained by the graphical user interface container object; and recording, in the computer, a containment relationship between the graphical user interface container object and the graphical user interface component object in a table that is external to the graphical user interface container object and the graphical user interface component object, wherein the table contains a plurality of entries, wherein each entry contains an identification of a container and an identification of a component, wherein the table defines a mapping between a plurality of components and a plurality of containers, wherein the first graphical user interface toolkit and the second graphical user interface toolkit define classes in an object-oriented programming language, and wherein the first graphical user interface toolkit is Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT) and the second graphical user interface toolkit is the other of Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT). - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computer program product in a tangible and computer readable medium comprising functional descriptive material that, when executed by a computer, causes the computer to perform actions that include:
-
providing a graphical user interface container object in a first graphical user interface toolkit, wherein the graphical user interface container object is incapable of recognizing containment relationships between the graphical user interface container object and any component objects from a second graphical user interface toolkit; generating a graphical user interface component object in the second graphical user interface toolkit; causing the graphical user interface component object to become contained by the graphical user interface container object; and a containment relationship between the graphical user interface container object and the graphical user interface component object in a table that is external to the graphical user interface container object and the graphical user interface component object, wherein the table contains a plurality of entries, wherein each entry contains an identification of a container and an identification of a component, wherein the table defines a mapping between a plurality of components and a plurality of containers, wherein the first graphical user interface toolkit and the second graphical user interface toolkit define classes in an object-oriented programming language, and wherein the first graphical user interface toolkit is Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT) and the second graphical user interface toolkit is the other of Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT). - View Dependent Claims (8, 9, 10, 11)
-
-
12. A data processing system comprising:
-
at least one processor; at least one data store accessible to the at least one processor; and a set of instructions in the at least one data store, wherein the at least one processor executes the set of instructions to perform actions of; providing a graphical user interface container object in a first graphical user interface toolkit, wherein the graphical user interface container object is incapable of recognizing containment relationships between the graphical user interface container object and any component objects from a second graphical user interface toolkit; generating a child graphical user interface component object in the second graphical user interface toolkit; causing the graphical user interface component object to become contained by the graphical user interface container object; and recording a containment relationship between the graphical user interface container object and the graphical user interface component object in a table external to the graphical user interface container object and the graphical user interface component object, wherein the table contains a plurality of entries, wherein each entry contains an identification of a container and an identification of a component, wherein the table defines a mapping between a plurality of components and a plurality of containers, wherein the first graphical user interface toolkit and the second graphical user interface toolkit define classes in an object-oriented programming language, and wherein the first graphical user interface toolkit is Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT and the second graphical user interface toolkit is the other of Abstract Windowing Toolkit (AWT) or Standard Widget Toolkit (SWT). - View Dependent Claims (13, 14, 15, 16)
-
Specification