Systems and methods for programming mobile devices
AssigneeExpress Mobile, Inc.
InventorsSteven H. Rempell, David Chrobak, Ken Brown
Life of this patent
Estimating the term…
Abstract
Embodiments of a system and method are described for generating and distributing programming to mobile devices over a network. Devices are provided with Players specific to each device and Applications that are device independent. Embodiments include a full-featured WYSIWYG authoring environment, including the ability to bind web components to objects.
Claims29
A system for generating code to provide content on a display of a device, said system comprising:
- computer memory storing:
- a) symbolic names required for evoking one or more web components each related to a set of inputs and outputs of a web service obtainable over a network, where the symbolic names are character strings that do not contain either a persistent address or pointer to an output value accessible to the web service, where each symbolic name has an associated data format class type corresponding to a subclass of User Interface (UI) objects that support the data format type of the symbolic name, and where each symbolic name has a preferred UI object, and
- b) an address of the web service;
- an authoring tool configured to:
- define a UI object for presentation on the display,
- where said defined UI object corresponds to a web component included in said,
- computer memory selected from a group consisting of an input of the web service and an output of the web service, where each defined UI object is either:
- 1) selected by a user of the authoring tool;
- or
- 2) automatically selected by the system as the preferred UI object corresponding to the symbolic name of the web component selected by the user of the authoring tool,
- access said computer memory to select the symbolic name corresponding to the web component of the defined UI object,
- associate the selected symbolic name with the defined UI object, where the selected symbolic name is only available to UI objects that support the defined data format associated with that symbolic name,
- store information representative of said defined UI object and related settings in a database;
- retrieve said information representative of said one or more said UI object settings stored in said database;
- and
- build an application consisting of one or more web page views from at least a portion of said database utilizing at least one player, where said player utilizes information stored in said database to generate for the display of at least a portion of said one or more web pages,
- wherein when the application and player are provided to the device and executed on the device, and
- when the user of the device provides one or more input values associated with an input symbolic name to an input of the defined UI object, the device provides the user provided one or more input values and corresponding input symbolic name to the web service, the web service utilizes the input symbolic name and the user provided one or more input values for generating one or more output values having an associated output symbolic name,
- and the player receives the output symbolic name and corresponding one or more output values and provides instructions for the display of the device to present an output value in the defined UI object.
A method of displaying content on a display of a device having a player and non-volatile computer memory storing symbolic names required for evoking one or more web components each related to a set of inputs and outputs of a web service obtainable over a network, where the symbolic names are character strings that do not contain either a persistent address or pointer to an output value accessible to the web service, where each symbolic name has an associated data format class type corresponding to a subclass of User Interface (UI) objects that support the data format type of the symbolic name, and where each symbolic name has a preferred UI object, and an address of the web service, said method comprising:
- defining a UI object for presentation on the display, where said UI object corresponds to a web component included in the computer memory, where said web component is selected from a group consisting of an input of a web service and an output of the web service, where each defined UI object is either:
- 1) selected by a user of the authoring tool;
- or 2) automatically selected by the system as the preferred UI object corresponding to a symbolic name of the web component selected by the user of the authoring tool;
- selecting the symbolic name corresponding to the web component of the defined UI object;
- associating the selected symbolic name with the defined UI object, where the selected symbolic name is only available to UI objects that support the defined data format associated with that symbolic name;
- storing information representative of said defined UI object and related settings in a database;
- retrieving said information representative of said one or more said UI object settings stored in said database;
- and
- building an application consisting of one or more web page views from at least a portion of said database utilizing the player, where said player utilizes information stored in said database to generate for the display of at least a portion of said one or more web pages,
- wherein, when the application and player are provided to the device and executed on the device, and when the user of the device provides one or more input values associated with an input symbolic name to an input of the defined UI object, 1) the device provides the user provided one or more input values and corresponding input symbolic name to the web service, 2) the web service utilizes the input symbolic name and the user provided one or more input values for generating one or more output values having an associated output symbolic name, and 3) the player receives the output symbolic name and corresponding one or more output values and provides instructions for the display of the device to present an output value in the defined UI object.
23-28. (canceled)
Dependencies are inferred from the claim text.