System and method for dynamically generating a graphical user interface
First Claim
Patent Images
1. A method for building a representation of a graphical user interface (GUI), comprising:
- generating a representation of the GUI from metadata, wherein the representation includes at least one control, wherein the at least one control has an interchangeable persistence mechanism;
driving the representation through at least one lifecycle stage by an interchangeable lifecycle component;
wherein the metadata can include at least one of;
hierarchical relationships among controls, control properties, and control event information;
wherein the representation can be driven through the at least one lifecycle stage by an interchangeable lifecycle component;
wherein an interface is provided to isolate details of the interchangeable lifecycle component from a control container to allow different lifecycle implementations to be interchangeable, the interchangeable lifecycle component further drives a control tree through different lifecycle stages, the control tree includes portal controls, desktop controls, page controls and portlet controls;
wherein the at least one control can advance through the at least one lifecycle stage in parallel with another control;
wherein the interchangeable life cycle component runs on at least one processor; and
wherein the life cycle stages include an “
Init”
stage that allows a control to perform initialization, a “
Load State”
stage that loads previously saved state from a request, a “
Create Child Controls”
stage that creates any child controls, a “
Load”
stage that obtains any external resources necessary for processing the request, a “
Raise Events”
stage that is a two phase stage where controls first indicate they want to raise events and then all controls who indicated this are allowed to raise events, a “
Pre-render”
stage that is the final stage before the rendering stages, a “
Save State”
stage in which all controls that want to save their states are given the opportunity to do so, a “
Render”
stage that is the stage where controls create their GUI representations and control how any children are rendered, a “
Unload”
stage that allows the control to free resources, and “
Dispose”
stage that does any final cleanup.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method for building a representation of a graphical user interface (GUI), comprising generating a class, generating a first representation of the GUI, wherein the class can produce a second representation GUI based on the first representation, generating a second representation of the GUI from the class, wherein the second representation includes at least one control, and wherein the first representation can include at least one of hierarchical relationships among controls, control properties, and control event information.
43 Citations
42 Claims
-
1. A method for building a representation of a graphical user interface (GUI), comprising:
-
generating a representation of the GUI from metadata, wherein the representation includes at least one control, wherein the at least one control has an interchangeable persistence mechanism; driving the representation through at least one lifecycle stage by an interchangeable lifecycle component; wherein the metadata can include at least one of;
hierarchical relationships among controls, control properties, and control event information;wherein the representation can be driven through the at least one lifecycle stage by an interchangeable lifecycle component; wherein an interface is provided to isolate details of the interchangeable lifecycle component from a control container to allow different lifecycle implementations to be interchangeable, the interchangeable lifecycle component further drives a control tree through different lifecycle stages, the control tree includes portal controls, desktop controls, page controls and portlet controls; wherein the at least one control can advance through the at least one lifecycle stage in parallel with another control; wherein the interchangeable life cycle component runs on at least one processor; and wherein the life cycle stages include an “
Init”
stage that allows a control to perform initialization, a “
Load State”
stage that loads previously saved state from a request, a “
Create Child Controls”
stage that creates any child controls, a “
Load”
stage that obtains any external resources necessary for processing the request, a “
Raise Events”
stage that is a two phase stage where controls first indicate they want to raise events and then all controls who indicated this are allowed to raise events, a “
Pre-render”
stage that is the final stage before the rendering stages, a “
Save State”
stage in which all controls that want to save their states are given the opportunity to do so, a “
Render”
stage that is the stage where controls create their GUI representations and control how any children are rendered, a “
Unload”
stage that allows the control to free resources, and “
Dispose”
stage that does any final cleanup. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A system for building a representation of a graphical user interface (GUI), comprising:
-
a first component operable to produce a second component and a metadata representation of the GUI; the second component operable to produce a hierarchical representation of the GUI based on the metadata, wherein the representation includes at least one control, wherein the at least one control has an interchangeable persistence mechanism; wherein the metadata can include at least one of;
hierarchical relationships among controls, control properties, and control event information;wherein the representation can be driven through at least one lifecycle stage by an interchangeable lifecycle component; wherein an interface is provided to isolate details of the interchangeable lifecycle component from a control container to allow different lifecycle implementations to be interchangeable; wherein the interchangeable lifecycle component further drives a control tree through different lifecycle stages, the control tree includes portal controls, desktop controls, page controls and portlet controls; wherein the at least one control can advance through the at least one lifecycle stage in parallel with another control; wherein the interchangeable life cycle component runs on at least one processor; and wherein the life cycle stages include an “
Init”
stage that allows a control to perform initialization, a “
Load State”
stage that loads previously saved state from a request, a “
Create Child Controls”
stage that creates any child controls, a “
Load”
stage that obtains any external resources necessary for processing the request, a “
Raise Events”
stage that is a two phase stage where controls first indicate they want to raise events and then all controls who indicated this are allowed to raise events, a “
Pre-render”
stage that is the final stage before the rendering stages, a “
Save State”
stage in which all controls that want to save their states are given the opportunity to do so, a “
Render”
stage that is the stage where controls create their GUI representations and control how any children are rendered, a “
Unload”
stage that allows the control to free resources, and “
Dispose”
stage that does any final cleanup. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
-
22. A system comprising:
-
a means for generating a first representation of a graphical user interface (GUI); a means for generating a second representation of the GUI from the first representation, wherein the second representation includes at least one control, wherein the at least one control has an interchangeable persistence mechanism; wherein metadata can include at least one of hierarchical relationships among controls, control properties, and control event information; wherein the second representation can be driven through at least one lifecycle stage by an interchangeable lifecycle component; wherein an interface is provided to isolate details of the interchangeable lifecycle component from a control container to allow different lifecycle implementations to be interchangeable; wherein the interchangeable lifecycle component further drives a control tree through different lifecycle stages, the control tree includes portal controls, desktop controls, page controls and portlet controls; wherein the at least one control can advance through the at least one lifecycle stage in parallel with another control; wherein the interchangeable life cycle component runs on at least one processor; and wherein the life cycle stages include an “
Init”
stage that allows a control to perform initialization, a “
Load State”
stage that loads previously saved state from a request, a “
Create Child Controls”
stage that creates any child controls, a “
Load”
stage that obtains any external resources necessary for processing the request, a “
Raise Events”
stage that is a two phase stage where controls first indicate they want to raise events and then all controls who indicated this are allowed to raise events, a “
Pre-render”
stage that is the final stage before the rendering stages, a “
Save State”
stage in which all controls that want to save their states are given the opportunity to do so, a “
Render”
stage that is the stage where controls create their GUI representations and control how any children are rendered, a “
Unload”
stage that allows the control to free resources, and “
Dispose”
stage that does any final cleanup. - View Dependent Claims (23, 24, 25, 26, 27, 28, 29, 30, 31, 32)
-
-
33. A machine readable storage medium having instructions stored thereon that when executed by a processor cause a system to:
-
generate a representation of a graphical user interface (GUI) from metadata, wherein the representation includes at least one control, wherein the at least one control has an interchangeable persistence mechanism; drive the representation through at least one lifecycle stage by an interchangeable lifecycle component; wherein the metadata can include at least one of;
hierarchical relationships among controls, control properties, and control event information;wherein the representation can be driven through the at least one lifecycle stage by the interchangeable lifecycle component; wherein an interface is provided to isolate details of the interchangeable lifecycle component from a control container to allow different lifecycle implementations to be interchangeable; wherein the interchangeable lifecycle component further drives a control tree through different lifecycle stages, the control tree includes portal controls, desktop controls, page controls and portlet controls; wherein the at least one control can advance through the at least one lifecycle stage in parallel with another control; wherein the interchangeable life cycle component runs on at least one processor; and wherein the life cycle stages include an “
Init”
stage that allows a control to perform initialization, a “
Load State”
stage that loads previously saved state from a request, a “
Create Child Controls”
stage that creates any child controls, a “
Load”
stage that obtains any external resources necessary for processing the request, a “
Raise Events”
stage that is a two phase stage where controls first indicate they want to raise events and then all controls who indicated this are allowed to raise events, a “
Pre-render”
stage that is the final stage before the rendering stages, a “
Save State”
stage in which all controls that want to save their states are given the opportunity to do so, a “
Render”
stage that is the stage where controls create their GUI representations and control how any children are rendered, a “
Unload”
stage that allows the control to free resources, and “
Dispose”
stage that does any final cleanup. - View Dependent Claims (34, 35, 36, 37, 38, 39, 40, 41, 42)
-
Specification
-
- Resources
Litigation Campaign Assessment
Thank you for your request. You will receive a custom alert email when the Litigation Campaign Assessment is available.
×
-
Current AssigneeOracle International Corporation (Oracle Corporation)
-
Original AssigneeBEA Systems Incorporated (Oracle Corporation)
-
InventorsHowes, Jason, Dew, Douglas, O'Neil, Edward, Giridhar, Sathyanarayana, Feit, Richard, Breeden, Timothy, Olander, Daryl B.
-
Primary Examiner(s)Sax; Steven P
-
Assistant Examiner(s)Belousov; Andrey
-
Application NumberUS10/789,140Publication NumberTime in Patent Office2,146 DaysField of Search715/854, 715/762, 715/763US Class Current715/854CPC Class CodesG06F 3/0482 Interaction with lists of s...G06F 3/0483 Interaction with page-struc...G06F 8/38 for implementing user inter...G06F 9/451 Execution arrangements for ...
