Abstract: The described embodiments distribute and synchronize objects in a network. More specifically, the described embodiments distribute copies of objects locally (i.e., store copies of objects in local address spaces). By storing a copy of a given object in a local address space, the object's methods may be executed locally, which can help to avoid excessive network traffic associated with remotely executing the object's methods. However, executing an object's methods locally can result in the state of the object (i.e., data associated with the object, etc.) becoming out of sync with other copies of the object in the network. To avoid issues associated with unsynchronized copies of the object in the network, the described embodiments use a policy that specifies conditions under which objects are to be synchronized.

Abstract: Methods for entering a full screen content viewing interface of an application are provided. In one aspect, a method includes receiving a request to provide content for display within a viewing region of an application and receiving a single touch input within the viewing region. The method also includes determining whether at least a portion of the content within the viewing region is obscured by a user interface element. When at least a portion of the content within the viewing region is obscured by the user interface element, the method includes removing the user interface element from the application. Systems and machine-readable media are also provided.

Abstract: The described embodiments distribute and synchronize objects in a network. More specifically, the described embodiments distribute copies of objects locally (i.e., store copies of objects in local address spaces). By storing a copy of a given object in a local address space, the object's methods may be executed locally, which can help to avoid excessive network traffic associated with remotely executing the object's methods. However, executing an object's methods locally can result in the state of the object (i.e., data associated with the object, etc.) becoming out of sync with other copies of the object in the network. To avoid issues associated with unsynchronized copies of the object in the network, the described embodiments use a policy that specifies conditions under which objects are to be synchronized.

Abstract: The described embodiments distribute and synchronize objects in a network. More specifically, the described embodiments distribute copies of objects locally (i.e., store copies of objects in local address spaces). By storing a copy of a given object in a local address space, the object's methods may be executed locally, which can help to avoid excessive network traffic associated with remotely executing the object's methods. However, executing an object's methods locally can result in the state of the object (i.e., data associated with the object, etc.) becoming out of sync with other copies of the object in the network. To avoid issues associated with unsynchronized copies of the object in the network, the described embodiments use a policy that specifies conditions under which objects are to be synchronized.

Abstract: Methods for entering a full screen content viewing interface of an application are provided. In one aspect, a method includes receiving a request to provide content for display within a viewing region of an application and receiving a single touch input within the viewing region. The method also includes determining whether at least a portion of the content within the viewing region is obscured by a user interface element. When at least a portion of the content within the viewing region is obscured by the user interface element, the method includes removing the user interface element from the application. Systems and machine-readable media are also provided.

Abstract: The described embodiments distribute and synchronize objects in a network. More specifically, the described embodiments distribute copies of objects locally (i.e., store copies of objects in local address spaces). By storing a copy of a given object in a local address space, the object's methods may be executed locally, which can help to avoid excessive network traffic associated with remotely executing the object's methods. However, executing an object's methods locally can result in the state of the object (i.e., data associated with the object, etc.) becoming out of sync with other copies of the object in the network. To avoid issues associated with unsynchronized copies of the object in the network, the described embodiments use a policy that specifies conditions under which objects are to be synchronized.

Abstract: A system for distributing and synchronizing objects. One or more embodiments of the invention provide for distributing copies of the objects locally. By copying objects into local address space, the object's methods may be executed locally thereby avoiding excessive network traffic. The state of the various object copies across a network may not be synchronized due to local changes and modifications. To synchronize the objects, one or more embodiments of the invention provide for the use of a policy that specifies conditions as to when objects are synchronized. Embodiments of the invention provide flexibility in setting the policy to accommodate varying applications. Alternatively, a policy may provide for synchronization based on the type or number of messages transmitted. In one or more embodiments, a default policy may be utilized that provides for the synchronization of local objects whenever a client issues a request from the remote server.

Abstract: The present invention comprises a novel system for managing changes to a graph of data bearing objects. In one embodiment, an object graph manager object referred to as an editing context is used to identify changes made to data bearing enterprise objects and to notify other interested objects when changes occur. As a result, data bearing objects need not themselves contain code necessary for monitoring changes. In another embodiment of the invention, the editing context is used to provide event-based “undo” capabilities. In another embodiment of the invention, each enterprise object has a primary key that is used to maintain the identification between an enterprise object instance and a corresponding database row. In another embodiment of the invention, multiple levels of editing contexts are used to provide multiple isolated object graphs, each of which allows independent manipulation of the underlying data bearing objects.

Abstract: A system for distributing and synchronizing objects. One or more embodiments of the invention provide for distributing copies of the objects locally. By copying objects into local address space, the object's methods may be executed locally thereby avoiding excessive network traffic. The state of the various object copies across a network may not be synchronized due to local changes and modifications. To synchronize the objects, one or more embodiments of the invention provide for the use of a policy that specifies conditions as to when objects are synchronized. Embodiments of the invention provide flexibility in setting the policy to accommodate varying applications. Alternatively, a policy may provide for synchronization based on the type or number of messages transmitted. In one or more embodiments, a default policy may be utilized that provides for the synchronization of local objects whenever a client issues a request from the remote server.

Abstract: A method and apparatus for distributing and synchronizing objects. One or more embodiments of the invention provide for distributing copies of the objects locally. By copying objects (including the data and behavior for the object) into local address space, the object's methods may be executed locally thereby avoiding excessive network traffic. The state of the various object copies across a network may not be synchronized due to local changes and modifications. To synchronize the objects, one or more embodiments of the invention provide for the use of a policy that specifies conditions as to when objects are synchronized. Embodiments of the invention provide flexibility in setting the policy to accommodate varying applications. For example, a policy may provide for synchronization that is based temporally (e.g., every 10 minutes or daily at 10:00 P.M.). Alternatively, a policy may provide for synchronization based on the type or number of messages transmitted.

Abstract: A method and apparatus for automatically and dynamically generating a user interface for a client based upon a database model. An application server creates a user interface description in accordance with the database model. The description is then distributed to the client, which interprets the description and creates the user interface therefrom.

Abstract: A method and apparatus for distributing and synchronizing objects. One or more embodiments of the invention provide for distributing copies of the objects locally. By copying objects (including the data and behavior for the object) into local address space, the object's methods may be executed locally thereby avoiding excessive network traffic. The state of the various object copies across a network may not be synchronized due to local changes and modifications. To synchronize the objects, one or more embodiments of the invention provide for the use of a policy that specifies conditions as to when objects are synchronized. Embodiments of the invention provide flexibility in setting the policy to accommodate varying applications. For example, a policy may provide for synchronization that is based temporally (e.g., every 10 minutes or daily at 10:00 P.M.). Alternatively, a policy may provide for synchronization based on the type or number of messages transmitted.

Abstract: The present invention comprises a novel system for managing changes to a graph of data bearing objects. In one embodiment, an object graph manager object referred to as an editing context is used to identify changes made to data bearing enterprise objects and to notify other interested objects when changes occur. As a result, data bearing objects need not themselves contain code necessary for monitoring changes. In another embodiment of the invention, the editing context is used to provide event-based “undo” capabilities. In another embodiment of the invention, each enterprise object has a primary key that is used to maintain the identification between an enterprise object instance and a corresponding database row. In another embodiment of the invention, multiple levels of editing contexts are used to provide multiple isolated object graphs, each of which allows independent manipulation of the underlying data bearing objects.

Abstract: A method and apparatus for distributing and synchronizing objects. One or more embodiments of the invention provide for distributing copies of the objects locally. By copying objects (including the data and behavior for the object) into local address space, the object's methods may be executed locally thereby avoiding excessive network traffic. The state of the various object copies across a network may not be synchronized due to local changes and modifications. To synchronize the objects, one or more embodiments of the invention provide for the use of a policy that specifies conditions as to when objects are synchronized. Embodiments of the invention provide flexibility in setting the policy to accommodate varying applications. For example, a policy may provide for synchronization that is based temporally (e.g., every 10 minutes or daily at 10:00 P.M.). Alternatively, a policy may provide for synchronization based on the type or number of messages transmitted.

Abstract: The present invention comprises a novel system for managing changes to a graph of data bearing objects. In one embodiment, an object graph manager object referred to as an editing context is used to identify changes made to data bearing enterprise objects and to notify other interested objects when changes occur. As a result, data bearing objects need not themselves contain code necessary for monitoring changes. In another embodiment of the invention, the editing context is used to provide event-based “undo” capabilities. In another embodiment of the invention, each enterprise object has a primary key that is used to maintain the identification between an enterprise object instance and a corresponding database row. In another embodiment of the invention, multiple levels of editing contexts are used to provide multiple isolated object graphs, each of which allows independent manipulation of the underlying data bearing objects.

Abstract: Methods, systems and machine readable media for operating a calendar in a data processing system. In one exemplary method of managing a calendar, which contains at least one event, said method comprises: making available the calendar in an electronic format; subscribing to said calendar; downloading said calendar from a host electronic device to a subscriber electronic device; and storing said calendar in said electronic format to form a local calendar.

Abstract: The current invention is about methods, systems and machine readable media for operating a calendar in a data processing system. In one exemplary method of managing said calendar, which contains at least one event, the method includes subscribing to said calendar which is available in an electronic format, downloading said calendar from a host electronic device to a subscriber electronic device, and storing said calendar in said electronic format to form a local calendar.

Abstract: A method and apparatus for automatically and dynamically generating a user interface for a client based upon a database model. An application server creates a user interface description in accordance with the database model. The description is then distributed to the client, which interprets the description and creates the user interface therefrom.

Abstract: Methods, systems and machine readable media for synchronising three or more electronic devices. In one exemplary method of synchronising three or more electronic devices, said method comprises: a) selecting at least one category of record for synchronisation; b) storing an original value and a changed value of each changed record from a selected record category; c) establishing an electronic connection between at least two devices; d) comparing the records of the selected record categories; e) determining any changed record; f) identifying the updated device with the changed record having an original value the same as the value of the record in the other previous device; and g) changing the value of the record in the previous device to the changed value.

Abstract: A method and apparatus for automatically and dynamically generating a user interface for a client based upon a database model. An application server creates a user interface description in accordance with the database model. The description is then distributed to the client, which interprets the description and creates the user interface therefrom.