Abstract: A direction and distance of movement of a display device as well as of a user of the display device are determined. Based on these determined directions and distances of movement, compensation to apply to content displayed on the display device to compensate for movement of the user with respect to the device is determined and applied to the content. A portion of the display device at which the user is looking can also be detected. The compensation is applied to the content only if applying the compensation would not result in the portion being positioned beyond the display device. If applying the compensation would result in the portion being positioned beyond the display device then appropriate corrective action is taken, such as not applying the compensation to the content.

Abstract: Mechanism for two portions of an application to communicate so as to facilitate a transition from synchronous to asynchronous communication. In order to prepare for a possible transition, data flow is monitored between the two portions of the application, each portion interacting with a different hardware entity. The data flow between the first portion and the second portion of the application is recorded. If the second hardware entity is not available at the time, the recorded data flow from the first portion may be replayed by the second portion of the application for the benefit of the second hardware entity. If the second portion of the application is to be reassigned to another hardware entity, the target hardware entity may be sent the second portion of the application, as well as the recorded information. This allows the target hardware entity to replay what has happened thus far for context.

Abstract: Mechanisms for a presentation module to perform distributed interfacing with an application across a plurality of hardware entities. The module identifies the hardware entities that are available to interface with endpoints of an application. The presentation module performs distribution of assignment of hardware entities to interact with the endpoints by, for each of at least some of the hardware entities, determining a subset of endpoints with which the corresponding hardware entities is to interface. Furthermore, the application is operated in that state to thereby detect interaction of at least some of the hardware entities with the application via at least some of the endpoints. Thus, distributed interfacing of hardware entities with an application is facilitated.

Abstract: Sharing an application in response to detecting one or more environmental events (such as user input). The mechanism operates multiple applications, and maintains a registry of endpoint interface entities. The endpoint interface entities may include hardware entities or hardware entities in association with environmental criteria. For each of at least some of the applications, the mechanism identifies at least one endpoint interface entity that is to interface with the endpoints at least a portion of the application. The selected endpoint interface entity is then allowed to interface with the application (or the portion). In some embodiments, the application is a transformation chain having endpoints.

Abstract: The incremental formulating an application in response to detecting events (such as user input) in an environment. Upon detecting one or more events, it is determined from this use input that an instance of a first transformation chain class is to be joined with an instance of a second transformation chain class. In response, the instance of the first transformation class is joined with the instance of the second transformation class along one or more data flow dependencies to formulate an aggregated instance. The aggregated instance may then be operated. This process may be repeated in response to different user input to thereby increase the size of the aggregated instance as more and more transformation chain instances join into the aggregated instance at appropriate chains of dependency.

Abstract: The automatic spawning of application in response to detected content in other communications. Such application spawning has the effect of enriching the original communication with the additional functionality of applications that accomplish and supplement the original communication. Such application spawning may be automatic, and responsive to monitoring of the content of the communication. Upon detecting that the content of the communication has satisfied summoning criteria, the application is summoned on a hardware entity associated with one or more of the participants in the communication. This may be accomplished while the communication is still ongoing.

Abstract: Automatically generating a software class that is compatible with a transformation chain class library. Such may be used to further populate the transformation chain class library with additional classes of software that was not originally generated as a transformation chain. In response to receiving a software representation, a dependency is identified in the software representation. It is then determined that the dependency corresponds to a dependency element of a transformation chain class of the transformation class library. Then, a software class is generated that corresponds to the software representation and that includes a dependency element that corresponds to the identified dependency, and that is recognized by a merging module as being compatible with the dependent element of the transformation chain class of the transformation chain class library. The software class may then be added to the transformation chain class library.

Abstract: Displaying application output in a manner that is not predetermined by the application, nor by the display. The computing system associated with the display accesses a set of information output by an application and to be displayed on a display. However, rather than explicit instructions on how to display being received from the application itself, the computing system instead accesses a set of one or more display rules that are associated with the set of information. The computing system then uses the set of one or more display rules to determine how to layout the set of information on the display. If the set of information were to change, the rules may be reevaluated to determine how the new information should be laid out. If the associated set of display rules were to also changed, the reevaluation would occur thereby resulting in a potentially different layout on the display.

Abstract: The automatic spawning of application in response to detected content in other communications. Such application spawning has the effect of enriching the original communication with the additional functionality of applications that accomplish and supplement the original communication. Such application spawning may be automatic, and responsive to monitoring of the content of the communication. Upon detecting that the content of the communication has satisfied summoning criteria, the application is summoned on a hardware entity associated with one or more of the participants in the communication. This may be accomplished while the communication is still ongoing.

Abstract: The splitting of an application in response to detected environmental events (such as user input). Such splitting may be performed for purposes of sharing the application. The application is a transformation chain instance. From the detected environmental event(s), it is determined that a portion transformation chain class is to be created from the larger transformation chain class of the application. In response, the portion transformation chain class is created, instantiated and operated. A sharing mechanism may be used to allow the split portion of the application to be shared with other entities without losing control.

Abstract: Automatically generating a software class that is compatible with a transformation chain class library. Such may be used to further populate the transformation chain class library with additional classes of software that was not originally generated as a transformation chain. In response to receiving a software representation, a dependency is identified in the software representation. It is then determined that the dependency corresponds to a dependency element of a transformation chain class of the transformation class library. Then, a software class is generated that corresponds to the software representation and that includes a dependency element that corresponds to the identified dependency, and that is recognized by a merging module as being compatible with the dependent element of the transformation chain class of the transformation chain class library. The software class may then be added to the transformation chain class library.

Abstract: The incremental formulating an application in response to detecting events (such as user input) in an environment. Upon detecting one or more events, it is determined from this use input that an instance of a first transformation chain class is to be joined with an instance of a second transformation chain class. In response, the instance of the first transformation class is joined with the instance of the second transformation class along one or more data flow dependencies to formulate an aggregated instance. The aggregated instance may then be operated. This process may be repeated in response to different user input to thereby increase the size of the aggregated instance as more and more transformation chain instances join into the aggregated instance at appropriate chains of dependency.

Abstract: Sharing an application in response to detecting one or more environmental events (such as user input). The mechanism operates multiple applications, and maintains a registry of endpoint interface entities. The endpoint interface entities may include hardware entities or hardware entities in association with environmental criteria. For each of at least some of the applications, the mechanism identifies at least one endpoint interface entity that is to interface with the endpoints at least a portion of the application. The selected endpoint interface entity is then allowed to interface with the application (or the portion). In some embodiments, the application is a transformation chain having endpoints.

Abstract: Mechanism for two portions of an application to communicate so as to facilitate a transition from synchronous to asynchronous communication. In order to prepare for a possible transition, data flow is monitored between the two portions of the application, each portion interacting with a different hardware entity. The data flow between the first portion and the second portion of the application is recorded. If the second hardware entity is not available at the time, the recorded data flow from the first portion may be replayed by the second portion of the application for the benefit of the second hardware entity. If the second portion of the application is to be reassigned to another hardware entity, the target hardware entity may be sent the second portion of the application, as well as the recorded information. This allows the target hardware entity to replay what has happened thus far for context.

Abstract: A user interface to share portions of applications between hardware entities and users thereof. The user interface is configured such that a user may select a portion of the user interface (and potentially also use redaction interactions) to identify an appropriate portion of the user interface to share. The user may also select a target hardware entity for that selected portion. Then, the portion of the application that generates that portion (appropriately redacted) of the user interface is shared with the selected target hardware entity. When that selected portion is run on that target entity, the associated user(s) will thus see the portion of the user interface (appropriately redacted). Accordingly, a user may quickly share portions of an application with another user via the use of refined portion selection interactions, and potentially also redaction user interactions.

Abstract: Mechanisms for a presentation module to perform distributed interfacing with an application across a plurality of hardware entities. The module identifies the hardware entities that are available to interface with endpoints of an application. The presentation module performs distribution of assignment of hardware entities to interact with the endpoints by, for each of at least some of the hardware entities, determining a subset of endpoints with which the corresponding hardware entities is to interface. Furthermore, the application is operated in that state to thereby detect interaction of at least some of the hardware entities with the application via at least some of the endpoints. Thus, distributed interfacing of hardware entities with an application is facilitated.

Abstract: A direction and distance of movement of a display device as well as of a user of the display device are determined. Based on these determined directions and distances of movement, compensation to apply to content displayed on the display device to compensate for movement of the user with respect to the device is determined and applied to the content. A portion of the display device at which the user is looking can also be detected. The compensation is applied to the content only if applying the compensation would not result in the portion being positioned beyond the display device. If applying the compensation would result in the portion being positioned beyond the display device then appropriate corrective action is taken, such as not applying the compensation to the content.

Abstract: A direction and distance of movement of a display device as well as of a user of the display device are determined. Based on these determined directions and distances of movement, compensation to apply to content displayed on the display device to compensate for movement of the user with respect to the device is determined and applied to the content. A portion of the display device at which the user is looking can also be detected. The compensation is applied to the content only if applying the compensation would not result in the portion being positioned beyond the display device. If applying the compensation would result in the portion being positioned beyond the display device then appropriate corrective action is taken, such as not applying the compensation to the content.

Abstract: A pattern matching framework for log analysis is described. In one or more implementations, one or more inputs are received via a user interface of a computing device that describe a filter pattern that specifies data that is to be matched and extracted from a log and a projection pattern that specifies how at least a portion of the data extracted using the filter pattern is to be output. A query is formed from the filter pattern and the projection pattern by the computing device that is configured to analyze the log.

Abstract: A cloud-based virtual world generation platform enables users to create content that can be incorporated into games as dynamic virtual worlds. The user-created content employs three-dimensional (3D) models of the user's environment using data that is captured by a camera system having depth sensing capabilities. A composition service exposed by the platform uses the captured data to generate a wireframe model that can be manipulated by the user with tools for applying surface textures (i.e., “skins”) and lighting, and for controlling other attributes and characteristics of the modeled environment. Other tools enable the user to select a particular physics engine that can control how the modeled user environment behaves during gameplay. The platform also exposes a rendering service with which a game can interact to access the user-generated content so that a modeled user environment can be utilized and incorporated into the game as a dynamic virtual world.