Explicitly defining user interface through class definition
First Claim
1. A system that facilitates generating a user interface, comprising the following components stored in computer storage media:
- a class component that defines properties and methods associated with one or more user interface actions;
a designer action object model that includes an action list, wherein the action list is an abstract base class from which various portions of user interface code can inherit, the action list being configured to specify interface actions or events in a generalized manner for appearance on a user interface, the action list further including properties and commands associated with the specified interface actions that change dynamically over time based on a state of at least one object, as well as one or more transitory components that are provided in the action list only until a particular task related to the action list has been achieved, the designer action object model being configured to perform the following;
merging a plurality of action lists from one or more different sources into a single action list for use by the class component and associating one or more action lists with the class component; and
a service component that determines which actions or interface options appear within the user interface and parses the class to automatically generate at least a portion of a user interface from the interface actions based at least in part upon the state of the at least one ether object, a development environment or an execution environment.
2 Assignments
0 Petitions
Accused Products
Abstract
The present invention relates to systems and methods that provide automatic generation of user interfaces via creation of a class-based model. A system is provided that facilitates generating a user interface. The system includes a class component to generally define properties and methods associated with one or more interface actions. A service component parses the class to automatically generate all or a portion of a user interface from the interface actions. Push and Pull-type models can be provided to facilitate merging of actions from various classes such as provided by third parties or from existing component developments.
-
Citations
23 Claims
-
1. A system that facilitates generating a user interface, comprising the following components stored in computer storage media:
-
a class component that defines properties and methods associated with one or more user interface actions; a designer action object model that includes an action list, wherein the action list is an abstract base class from which various portions of user interface code can inherit, the action list being configured to specify interface actions or events in a generalized manner for appearance on a user interface, the action list further including properties and commands associated with the specified interface actions that change dynamically over time based on a state of at least one object, as well as one or more transitory components that are provided in the action list only until a particular task related to the action list has been achieved, the designer action object model being configured to perform the following;
merging a plurality of action lists from one or more different sources into a single action list for use by the class component and associating one or more action lists with the class component; anda service component that determines which actions or interface options appear within the user interface and parses the class to automatically generate at least a portion of a user interface from the interface actions based at least in part upon the state of the at least one ether object, a development environment or an execution environment. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
-
16. A computer readable medium having computer readable instructions stored thereon for implementing the following components comprising at least:
-
an abstract class component that defines properties and methods associated with one or more interface actions, wherein one or more action lists comprised within the abstract class component are edited by a developer and parsed to determine which actions or events appear on a user interface derived from the class component, and wherein the class component is associated with a designer action object model that at least one of specifies a list of properties and commands that includes an action list, wherein the action list is an abstract base class from which various portions of user interface code can inherit, the action list being configured to specify interface actions or events in a generalized manner for appearance on a user interface, the action list further including properties and commands associated with the specified interface actions that change dynamically over time based on a state of at least one object, as well as one or more transitory components that are provided in the action list only until a particular task related to the action list has been achieved, the designer action object model being configured to perform the following;
merging a plurality of action lists from one or more different sources into a single action list for use by the class component and associating one or more action lists with the class component;a service component that overrides the abstract class component to provide a model for at least a portion of a user interface; and a generating component for automatically generating at least a portion of the interface from the interface actions based at least in part upon the state of the at least one object.
-
-
17. A system that facilitates generation of a user interface, comprising the following means executed by a processor:
-
means for defining abstract class parameters representative of methods and properties of an interface, which class parameters are edited by a developer; means for specifying a list of properties and commands, wherein the means for specifying includes a designer action object model that includes an action list, wherein the action list is an abstract base class from which various portions of user interface code can inherit, the action list being configured to specify interface actions or events in a generalized manner for appearance on a user interface, the action list further including properties and commands associated with the specified interface actions that change dynamically over time based on a state of at least one object, as well as one or more transitory components that are provided in the action list only until a particular task related to the action list has been achieved, the designer action object model being configured to perform the following;
merging a plurality of action lists from one or more different sources into a single action list for use by the class component and associating one or more action lists with the class component;means for identifying a property or a command to be used at a specific time in the user interface from the list of properties and commands; means for parsing the class parameters; and means for automatically generating at least a portion of the interface based in part on the abstract class parameters. - View Dependent Claims (18)
-
-
19. A method that facilitates automatic generation of a user interface, comprising:
-
defining properties and methods associated with one or more user interface actions; providing a designer action object model that includes an action list, wherein the action list is an abstract base class from which various portions of user interface code can inherit, the action list being configured to specify interface actions or events in a generalized manner for appearance on a user interface, the action list further including properties and commands associated with the specified interface actions that change dynamically over time based on a state of at least one object, as well as one or more transitory components that are provided in the action list only until a particular task related to the action list has been achieved, the designer action object model being configured to perform the following;
merging a plurality of action lists from one or more different sources into a single action list for use by the class component and associating one or more action lists with the class component; anddetermining which actions or interface options appear within the user interface and parses the class to automatically generate at least a portion of a user interface from the interface actions based at least in part upon the state of the at least one object, a development environment or an execution environment. - View Dependent Claims (20)
-
-
21. A computer readable storage medium having a data structure stored thereon, comprising:
-
a class component to store properties and methods relating to an user interface, wherein the class component is associated with a designer action object model that includes an action list, wherein the action list is an abstract base class from which various portions of user interface code can inherit, the action list being configured to specify interface actions or events in a generalized manner for appearance on a user interface, the action list further including properties and commands associated with the specified interface actions that change dynamically over time based on a state of at least one object, as well as one or more transitory components that are provided in the action list only until a particular task related to the action list has been achieved, the designer action object model being configured to perform the following;
merging a plurality of action lists from one or more different sources into a single action list for use by the class component and associating one or more action lists with the class component;the one or more action lists comprised within the class component that are edited by a developer and are parsed to determine which actions or events appear on the user interface derived from the class component; a first field defining at least one interface component associated with the methods; a second field defining at least one editor component associated with the properties; and a generating component for automatically generating at least a portion of the interface from the interface actions based at least in part upon the state of the at least one object. - View Dependent Claims (22, 23)
-
Specification