Abstract: A system and method for determining whether a flick gesture has occurred is described. A flick gesture is a simple gesture that may be easily detected and is characterized by minimal interference with other applications or gestures.

Abstract: In a main computer system coupled to an auxiliary display device, described is an interface set for implementation by an auxiliary display device driver, to couple the driver to an auxiliary display platform. Commands received from the auxiliary display platform may be handled by code external to the driver, such as a class extension object. For example, the class extension object may interpret and/or translate commands received from the auxiliary display platform into a format understood by the driver code. The auxiliary display device driver may then provide corresponding command information including data to the auxiliary display device via the transport. Event data may be returned from the auxiliary display device driver via the interface set to the class extension object, such that corresponding event information, e.g., received at the auxiliary display device, may be returned to the auxiliary display platform.

Abstract: In a main computer system coupled to an auxiliary display device, described is an interface set for implementation by an auxiliary display device driver, to couple the driver to an auxiliary display platform. Commands received from the auxiliary display platform may be handled by code external to the driver, such as a class extension object. For example, the class extension object may interpret and/or translate commands received from the auxiliary display platform into a format understood by the driver code. The auxiliary display device driver may then provide corresponding command information including data to the auxiliary display device via the transport. Event data may be returned from the auxiliary display device driver via the interface set to the class extension object, such that corresponding event information, e.g., received at the auxiliary display device, may be returned to the auxiliary display platform.

Abstract: A system and method for determining whether a flick gesture has occurred is described. A flick gesture is a simple gesture that may be easily detected and is characterized by minimal interference with other applications or gestures.

Abstract: Described is a system and method including an auxiliary display platform having an interface (API) set that provides a way for client applications running on a main computer system to interact with various types of auxiliary displays, irrespective of differences between various device implementations. Interaction includes displaying content and notifications provided by the application, and returning events to the application. In one implementation the API set comprises a set of COM objects that register and perform configuration checks of a client application, send content and notifications to attached devices, and return events from the attached devices. The application may send data to an endpoint corresponding to a communication destination (e.g., a particular auxiliary device application) and a contract (e.g., a format) for the data. The platform and API set thus provide an abstraction layer for applications to provide information independent of any particular auxiliary device implementation.

Abstract: Described is a technology by which a device pre-enables application programs of a computer system to work with the device when the device is connected to the computer system. A set of data is obtained from a device, such as by an installer at installation time. The set of data includes information that identifies one or more computer system application programs that the device desires to work with when each application program runs. When the data set is obtained, the application program is enabled (e.g., given appropriate permissions) such that the application program may communicate data with the device when the program is run on the computer system. In one implementation, a device driver provides an installer with access to the data set, which may also include additional information such as application configuration parameters. The installer may be automatically run on the computer system upon initial device detection.

Abstract: A system and method for determining whether a flick gesture has occurred is described. A flick gesture is a simple gesture that may be easily detected and is characterized by minimal interference with other applications or gestures.

Abstract: Described is a technology by which an application program such as a gadget may communicate with a sidebar program to output content for consumption by an auxiliary display device. The gadget may communicate with the sidebar program via sidebar APIs, and in turn the sidebar program communicates with an auxiliary display device platform via auxiliary display device APIs. Among its capabilities, the sidebar program may install gadgets on a host computer system, and upon detecting that the host computer system is configured to operate with an auxiliary display device, may install the gadget such that the gadget is configured to work with an auxiliary display device. The installation may be accomplished by having the sidebar program write information to a system registry.

Abstract: A system and method for determining whether a flick gesture has occurred is described. A flick gesture is a simple gesture that may be easily detected and is characterized by minimal interference with other applications or gestures.

Abstract: A system and method for determining whether a flick gesture has occurred is described. A flick gesture is a simple gesture that may be easily detected and is characterized by minimal interference with other applications or gestures.

Abstract: Described is a system and method in which pen gestures cause a mode to be entered in which a computing device acts as if a modifier key (e.g., Control, Alt, or Shift) was being pressed. This is accomplished by a pen driver sending a modifier key down to the keyboard and mouse input subsystem. Modifier key behavior is thus provided, including at times when a keyboard is not readily available. While in the modifier key mode, additional gestures can be input, including a gesture that results in the computing device acting as if multiple modifier keys are pressed. Also, while in the mode, visual feedback may be provided to indicate the mode is active. The mode may be exited by sending a corresponding modifier key up, and the exit may be triggered in various ways, including by other gestures, mouse or pen events, and certain keyboard input.

Abstract: Embodiments of the invention are directed to a software platform capable of sending data to auxiliary-display devices that are either connected (e.g., wirelessly) to a computing device or associated with the computing device in some way. Embodiments of the invention relate to a mobile auxiliary-display device model that enables communication between a computing device and an auxiliary-display device. Embodiments of the invention are directed to a driver model capable of communicating with wireless devices, such as cell phones, personal digital assistants and the like, via a wireless communication channel, such as Bluetooth® wireless technology. Embodiments of the invention are directed to software that executes on the computing device and software that executes on a mobile auxiliary-display device.

Abstract: Described is a technology by which a specific gadget program is installed (e.g., created) on a main host computer system that receives data (e.g., an RSS feed) from a distribution source, in which the feed data contains the information needed to install the gadget. Once installed, gadget is then used to receive content from its corresponding data source and provide the content for display on an auxiliary display device. The feed data may include metadata such as a gadget-related enclosure, from which the installer may register information corresponding to the metadata in a registry or the like, and associate the gadget with one or more particular auxiliary displays. By processing the metadata, the other gadget is installed and then run as needed to handle content data from the corresponding data source, in order to render content on an auxiliary display.

Abstract: Described is a technology by which an application program such as a gadget may communicate with a sidebar program to output content for consumption by an auxiliary display device. The gadget may communicate with the sidebar program via sidebar APIs, and in turn the sidebar program communicates with an auxiliary display device platform via auxiliary display device APIs. Among its capabilities, the sidebar program may install gadgets on a host computer system, and upon detecting that the host computer system is configured to operate with an auxiliary display device, may install the gadget such that the gadget is configured to work with an auxiliary display device. The installation may be accomplished by having the sidebar program write information to a system registry.

Abstract: Described is a technology by which a device pre-enables application programs of a computer system to work with the device when the device is connected to the computer system. A set of data is obtained from a device, such as by an installer at installation time. The set of data includes information that identifies one or more computer system application programs that the device desires to work with when each application program runs. When the data set is obtained, the application program is enabled (e.g., given appropriate permissions) such that the application program may communicate data with the device when the program is run on the computer system. In one implementation, a device driver provides an installer with access to the data set, which may also include additional information such as application configuration parameters. The installer may be automatically run on the computer system upon initial device detection.

Abstract: In a main computer system coupled to an auxiliary display device, described is an interface set for implementation by an auxiliary display device driver, to couple the driver to an auxiliary display platform. Commands received from the auxiliary display platform may be handled by code external to the driver, such as a class extension object. For example, the class extension object may interpret and/or translate commands received from the auxiliary display platform into a format understood by the driver code. The auxiliary display device driver may then provide corresponding command information including data to the auxiliary display device via the transport. Event data may be returned from the auxiliary display device driver via the interface set to the class extension object, such that corresponding event information, e.g., received at the auxiliary display device, may be returned to the auxiliary display platform.

Abstract: Described is a system and method comprising a content format by which client programs running on a main computer system may provide data to various types of auxiliary display devices. The format, which may be XML-based, provides menu pages comprising a list of selectable items, content pages comprising text and images, and dialog pages providing text, images and one or more actionable options. The text and images may be accompanied by requested formatting information, e.g., specifying emphasis, color, alignment, wrapping and/or fit to the screen. An auxiliary device can parse the content to display as much as possible, particularly information recognized (via content tags) as significant, and use the formatting information to the extent of its capabilities. Virtual buttons may be defined for page navigation and/or item selection. Pages of the content format may be cached for operation when the main computer system is offline from the auxiliary display device.

Abstract: The invention relates to improved systems and methods for communicating information between an auxiliary display device and a primary display device. Methods and systems for automatic cross-display coordination between an auxiliary and primary display device through the use of executable command lines are provided. In at least one embodiment, a user of a user computer may determine what features of an application are associated with executable command lines and displayed on an auxiliary device. In yet other embodiments, an API is provided to allow a user to select or manually enter command lines to execute on a primary display device. Yet further aspects of the invention, the auxiliary display device is used to remotely produce a visual output on a primary display device.

Abstract: Described is a system and method in which pen gestures cause a mode to be entered in which a computing device acts as if a modifier key (e.g., Control, Alt, or Shift) was being pressed. This is accomplished by a pen driver sending a modifier key down to the keyboard and mouse input subsystem. Modifier key behavior is thus provided, including at times when a keyboard is not readily available. While in the modifier key mode, additional gestures can be input, including a gesture that results in the computing device acting as if multiple modifier keys are pressed. Also, while in the mode, visual feedback may be provided to indicate the mode is active. The mode may be exited by sending a corresponding modifier key up, and the exit may be triggered in various ways, including by other gestures, mouse or pen events, and certain keyboard input.