Abstract: The present invention extends to methods, systems, and computer program products for using cinematic techniques to present data. Embodiments of the invention can be used to infer and generate cinematic techniques or combinations thereof based on a model and user action. Cinematic techniques can be used to meet the data exploration and analysis requirements of a user. As such, embodiments of the invention permit users (including non-programmers) to employ cinematic techniques (possibly in combination with other techniques) to gain insights into their data and also convey appropriate emotional messages.

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: Synthesizing of information and application user interface elements into a continuous stream form. This is done by adjusting a level of cinematicity to be applied to a session of information as the session is presented. Higher level cinematicity use higher degrees of movement in presenting user interface elements representing the information. In contrast, lower levels of cinematicity use lower or no movement of user interface elements representing the information.

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 compilation of a transformation chain of a recalculation user interface that displays an electronic canvas that contains one or more displayed result of a transformation chain. The transformation chain includes transforms between a respective data source and data sink. User editing of the recalculation user interface could cause one or more of the transforms to be re-executed, thereby causing recalculation. The compilation involves analyzing the transformation chain of the recalculation user interface for dependencies to create a dependency graph of dependencies between entities. For instance, some dependencies might be between entities so as to indicate that if one entity is evaluated, then the other should be also. The dependency graph is then used to create a lower level of execution steps. The dependency graph is further provided to a runtime for the program, so that the dependency graph may be available during operation of the recalculation user interface.

Abstract: The present invention extends to methods, systems, and computer program products for using cinematic techniques to present data. Embodiments of the invention can be used to infer and generate cinematic techniques or combinations thereof based on a model and user action. Cinematic techniques can be used to meet the data exploration and analysis requirements of a user. As such, embodiments of the invention permit users (including non-programmers) to employ cinematic techniques (possibly in combination with other techniques) to gain insights into their data and also convey appropriate emotional messages.

Abstract: Operating an application in response to spatial status of objects within a physical environment in which the application operates. A system detects the spatial status (e.g., orientation, movement, position, and so forth) of multiple environmental objects that operate within a physical environment from which input is provided to, and to which output is provided from, an application. The relationship between at least some different environmental objects result in altered a behavior of the application. The spatial status of at least some of the environmental objects is subject to change. Thus, a mechanism is described that allows an application to adjust in a manner that is highly responsive to the physical environment in which the application interfaces.

Abstract: Mechanisms for rendering on an output device, such as a display. An actuator module is associated with a rendering rendered on an output device. If the actuator module is activated, the application itself is summoned and/or augmented so that application output is rendered on the output device. The application output is specific to the prior state of the rendering on the output devise. Thus, one user that activates the actuator module in one context may have a completely different experience that a user that activates the actuator module in another context, as the augmentation of the application is appropriate and matched to the current rendering context. The principles apply even across different applications. Thus, the actuator module may become a ubiquitous button that may be used by any user to enrich any application appropriate to the current context of that application.

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 rendering of information on an output device when there is a set of information rendered on the output device that is shareable to a second output device. In this context, shareable means that the application that generates the information is extracted and run instead on behalf of the second output device to render the information on the second output device. In addition, there is output an emphasis that aids the user in understanding that there is the technical capability to share the set of information in this manner. Thus, the user may be informed and more aptly initiate the technical ability to achieve the sharing of the set of information with the second output device.

Abstract: Gesture recognition and sharing technology that allows a user to gesture to share portions of a user interface. Upon recognizing when a portion selection gesture has been entered on a display, an associated portion of the user interface is identified based on spatial relation of the portion selection gesture. In response, the system causes the associated portion of the user interface to be shared for display on a remote display, perhaps by even sharing the portion of the application that generated the user interface portion. The portion selection gesture may be a position gesture that is centered on the portion to be displayed. The portion selection gesture may be a negative gesture that centers over a portion of the user interface not to be shared. By appropriate combination of position and negative gestures, fine-grained and efficient definition of the set of shared user interface element(s) may be made.

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: 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: 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: 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: 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 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: 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 facilitating of output on an output device that receives output from an application that actually redefines during use. An initial output of information to be presented is caused to be rendered on the output device. Then, upon encountering that the application itself is redefined, the output is altered, and the output device updated. Furthermore, there may be other triggers that change the output on the output device including a change in allocation of output between multiple output devices, a change in users of the output device, a change in position of one or more users with respect to the output device, a change in control of one or more users with respect to the output device, a change in authorization of one or more users with respect to the output device or the information outputted. Accordingly, the output device may be updated appropriately even in a dynamic computing environment.

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.