Abstract: A server is implemented with a modified file open action, which, when a user performs the modified open, initially opens a file without locking the file. When a user indicates (either explicitly or implicitly) that the user is attempting to or intending to open the file, the file can then be locked for editing. In this way, the default action when a user requests a file is to open the file without denying other users access to the file. Then, when the user indicates that editing should occur, the lock for the file is obtained.

Abstract: A server is implemented with a modified file open action, which, when a user performs the modified open, initially opens a file without locking the file. When a user indicates (either explicitly or implicitly) that the user is attempting to or intending to open the file, the file can then be locked for editing. In this way, the default action when a user requests a file is to open the file without denying other users access to the file. Then, when the user indicates that editing should occur, the lock for the file is obtained.

Abstract: A server is implemented with a modified file open action, which, when a user performs the modified open, initially opens a file without locking the file. When a user indicates (either explicitly or implicitly) that the user is attempting to or intending to open the file, the file can then be locked for editing. In this way, the default action when a user requests a file is to open the file without denying other users access to the file. Then, when the user indicates that editing should occur, the lock for the file is obtained.

Abstract: An apparatus and method provide a companion application via a companion application corresponding to a host window provided by a host application, the companion window providing information or metadata descriptive of data in the host window. The host application and companion applications may be separate applications such that the host application is unaware of the companion application. The companion application may hook into the host application (e.g., via an application programming interface) and may monitor host application activities and/or data. Based on identification of data or events in the host application, the companion application may obtain information characterizing or providing a context for data provided by the host application. The host window and companion window may be attached to each other, the host window providing host application data and the companion window providing data describing the host application data.

Abstract: Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Abstract: Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Abstract: Systems, methods, and user interfaces for gathering and using awareness information with common awareness functionality accessible to multiple applications are disclosed. Such systems, methods, and user interfaces may aggregate awareness information from multiple sources and provide awareness data and other derived information to multiple destinations. In some implementations, such systems and methods may provide additional functionality related to awareness information, such as common user interfaces that display awareness information or mechanisms for determining the relevance of particular pieces of awareness information.

Abstract: A server is implemented with a modified file open action, which, when a user performs the modified open, initially opens a file without locking the file. When a user indicates (either explicitly or implicitly) that the user is attempting to or intending to open the file, the file can then be locked for editing. In this way, the default action when a user requests a file is to open the file without denying other users access to the file. Then, when the user indicates that editing should occur, the lock for the file is obtained.

Abstract: An apparatus and method provide a companion application via a companion application corresponding to a host window provided by a host application, the companion window providing information or metadata descriptive of data in the host window. The host application and companion applications may be separate applications such that the host application is unaware of the companion application. The companion application may hook into the host application (e.g., via an application programming interface) and may monitor host application activities and/or data. Based on identification of data or events in the host application, the companion application may obtain information characterizing or providing a context for data provided by the host application. The host window and companion window may be attached to each other, the host window providing host application data and the companion window providing data describing the host application data.

Abstract: An apparatus and method provide a companion application via a companion application corresponding to a host window provided by a host application, the companion window providing information or metadata descriptive of data in the host window. The host application and companion applications may be separate applications such that the host application is unaware of the companion application. The companion application may hook into the host application (e.g., via an application programming interface) and may monitor host application activities and/or data. Based on identification of data or events in the host application, the companion application may obtain information characterizing or providing a context for data provided by the host application. The host window and companion window may be attached to each other, the host window providing host application data and the companion window providing data describing the host application data.

Abstract: Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Abstract: Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Abstract: Identifying program module functionality needed by a computer when disconnected from a network is disclosed. A document identification engine (DIE) creates a list of files stored locally on the computer. The DIE sends the list of files to a document mapping engine (DME). The DME identifies a proper handler routine for each file in the list of files and sends each file to the proper handler routine(s). The handler routine(s) identifies the application functionality needed to execute each file. The application functionality may include products, features and components. A migration engine (ME) determines the current status of the needed application functionality. If the status of the needed application functionality indicates that the needed application functionality is not installed locally on the computer, then the ME installs the needed application functionality to the computer.

Abstract: Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Abstract: Systems, methods, and user interfaces for gathering and using awareness information with common awareness functionality accessible to multiple applications are disclosed. Such systems, methods, and user interfaces may aggregate awareness information from multiple sources and provide awareness data and other derived information to multiple destinations. In some implementations, such systems and methods may provide additional functionality related to awareness information, such as common user interfaces that display awareness information or mechanisms for determining the relevance of particular pieces of awareness information.

Abstract: Data files, applications and/or corresponding user interfaces may be accessed at a device that collaborates in a mesh. The mesh may include any number or type of devices that collaborate in a network. Data, applications and/or corresponding user interfaces may be stored within a core object that may be shared over the mesh. Information in the core object may be identified with a corresponding user such that a user may use any collaborating device in the mesh to access the information. In one example, the information is stored remotely from a device used to access the information. A remote source may store the desired information or may determine the storage location of the desired information in the mesh and may further provide the desired information to a corresponding user.

Abstract: An apparatus and method provide a companion application via a companion application corresponding to a host window provided by a host application, the companion window providing information or metadata descriptive of data in the host window. The host application and companion applications may be separate applications such that the host application is unaware of the companion application. The companion application may hook into the host application (e.g., via an application programming interface) and may monitor host application activities and/or data. Based on identification of data or events in the host application, the companion application may obtain information characterizing or providing a context for data provided by the host application. The host window and companion window may be attached to each other, the host window providing host application data and the companion window providing data describing the host application data.