Abstract: An organization mode in a user interface that displays multiple user interface elements. The multiple user interface elements fit over a grid positions that are at least conceptually imposed over a canvas. In organization mode, the grid positions are displayed, allowing the user to more easily see where user interface elements may be placed. As the user moves and/or resizes a user interface element, one or more corresponding grid positions are highlighted to show where the user interface element would be placed if the move or resize operation were to conclude at that moment. The organization mode may also provide a contextual actions menu with respect to a particular user interface element. The contextual actions menu includes multiple organization mode commands, including one or more that may be directed selected from the contextual actions menu to invoke the command.

Abstract: A user interface control that has different logic components for processing different role logic depending on a role that is played by the user interface control. The user interface control may also have a general function component that performs general functions that may be common across multiple user interface controls. Also, a protocol for use in communicating between two user interface controls to establish a communications link. A first user interface control requests information from a second user interface control, which then obtains the requested information. The second user interface control then provides the requested information to the first user interface control, and then awaits the validation of the requested information.

Abstract: An organization mode in a user interface that displays multiple user interface elements. The multiple user interface elements fit over a grid positions that are at least conceptually imposed over a canvas. In organization mode, the grid positions are displayed, allowing the user to more easily see where user interface elements may be placed. As the user moves and/or resizes a user interface element, one or more corresponding grid positions are highlighted to show where the user interface element would be placed if the move or resize operation were to conclude at that moment. The organization mode may also provide a contextual actions menu with respect to a particular user interface element. The contextual actions menu includes multiple organization mode commands, including one or more that may be directed selected from the contextual actions menu to invoke the command.

Abstract: An organization mode in a user interface that displays multiple user interface elements. The multiple user interface elements fit over a grid positions that are at least conceptually imposed over a canvas. In organization mode, the grid positions are displayed, allowing the user to more easily see where user interface elements may be placed. As the user moves and/or resizes a user interface element, one or more corresponding grid positions are highlighted to show where the user interface element would be placed if the move or resize operation were to conclude at that moment. The organization mode may also provide a contextual actions menu with respect to a particular user interface element. The contextual actions menu includes multiple organization mode commands, including one or more that may be directed selected from the contextual actions menu to invoke the command.

Abstract: Generally in a computing environment, executing work based on time (i.e. according to a predetermined schedule) is a common need. However, in cloud based systems, scheduled work may be expensive to customers as generally customers rent system resources. Thus, having a processor dedicated to performing actions that have been pre-scheduled can be expensive. This application describes using a continuation-based runtime for scheduling time-bound and/or periodic work in a distributed (i.e. cloud) system. A system architecture and computer-implemented method are described that deploy an environment-independent action to a remote-based system (such as a cloud computing system, for example). The action is limited to using a predetermined amount of resources and is limited to simple, non-cpu intensive orchestrations of network calls.

Abstract: A model for displaying multiple user interface elements such that each control includes a container that includes standard functionality across at least a majority of the user interface elements. For instance, such standard functionality might include a part status indication, a title, a content status indication, a command invocation function, a part resizing function, and so forth. The model may also provide for standardization of resizing of user interface elements. For a given user interface element, there would be a predetermined number of possible size and shapes, each corresponding to a different projection of data. For instance, all of the user interface elements on a screen may fall within the predetermined number of possible size and shapes, thereby allowing more functional layout of the user interface on the display.

Abstract: A gallery user interface element that includes multiple selectable service user interface elements. Each of the selectable service user interface elements, when selected, initiates a corresponding predetermined action. Thus, the gallery may be used to initiate any number of predetermined actions by selecting appropriate service user interface elements. The predetermined actions may be performed by a number of user interface elements that are collectively offered by a variety of different applications, application extensions, or the system itself. The predetermined actions may include at least one predetermined action that extends an extendible canvas with one or more additional user interface elements. The gallery may include multiple pinnable elements and have different versions depending on a context in which the gallery was opened.

Abstract: A hierarchy of controls and parts, that are each in accordance with constraints of a computing executing context. A control is executable code that performs a function and which may impart a visualization. A part is a unit of visualization container that has its own visualization and/or shows visualizations from one or more compliant controls associated with the part.

Abstract: A multi-act creation user interface element that is displayed when a user instructs a computing system to initiate creation of a resource that has multiple associated creation processing acts. For each of some or all of the creation processing acts, the multi-act creation user interface element causes a set of one or more controls to appear, which the user may then enter creation information into. The multi-step creation user interface element persists creation information so entered so that the creation information is available for further creation processing acts.

Abstract: Embodiments are directed to presenting multiple projections of a declarative program and to presenting partial projections of a declarative program. In one scenario, a computer system establishes a declarative program that includes various artifacts. The computer system displays a first projection of the declarative program, which includes one or more elements of a workflow. The computer system then determines that an additional projection is to be displayed in addition to the first projection, and presents a second projection based on the artifacts of the declarative program. The second projection illustrates the artifacts in a form different than that shown in the first projection, and is presented in addition to the first projection. In some cases, the computer system further receives an input and edits the declarative program according to the received input. The edits to the declarative program are substantially lossless, and can be performed using partial or full projections.

Abstract: Scheduling a scheduled and optionally periodic action in a remote based system. The method includes deploying an environment independent action to a remote based system. The action is limited to using a predetermined amount of resources and is limited to simple, non-cpu intensive orchestrations of network calls. The method further includes defining a schedule for the action to be executed. Calling the action at the remote based system based on the schedule in a processor independent fashion such that state of the action is maintained independent of the processor that the action is being executed on.

Abstract: Generally in a computing environment, executing work based on time (i.e. according to a predetermined schedule) is a common need. However, in cloud based systems, scheduled work may be expensive to customers as generally customers rent system resources. Thus, having a processor dedicated to performing actions that have been pre-scheduled can be expensive. This application describes using a continuation-based runtime for scheduling time-bound and/or periodic work in a distributed (i.e. cloud) system. A system architecture and computer-implemented method are described that deploy an environment-independent action to a remote-based system (such as a cloud computing system, for example). The action is limited to using a predetermined amount of resources and is limited to simple, non-cpu intensive orchestrations of network calls.

Abstract: An organization mode in a user interface that displays multiple user interface elements. The multiple user interface elements fit over a grid positions that are at least conceptually imposed over a canvas. In organization mode, the grid positions are displayed, allowing the user to more easily see where user interface elements may be placed. As the user moves and/or resizes a user interface element, one or more corresponding grid positions are highlighted to show where the user interface element would be placed if the move or resize operation were to conclude at that moment. The organization mode may also provide a contextual actions menu with respect to a particular user interface element. The contextual actions menu includes multiple organization mode commands, including one or more that may be directed selected from the contextual actions menu to invoke the command.

Abstract: A gallery user interface element that includes multiple selectable service user interface elements. Each of the selectable service user interface elements, when selected, initiates a corresponding predetermined action. Thus, the gallery may be used to initiate any number of predetermined actions by selecting appropriate service user interface elements. The predetermined actions may be performed by a number of user interface elements that are collectively offered by a variety of different applications, application extensions, or the system itself. The predetermined actions may include at least one predetermined action that extends an extendible canvas with one or more additional user interface elements. The gallery may include multiple pinnable elements and have different versions depending on a context in which the gallery was opened.

Abstract: A user interface control that has different logic components for processing different role logic depending on a role that is played by the user interface control. The user interface control may also have a general function component that performs general functions that may be common across multiple user interface controls. Also, a protocol for use in communicating between two user interface controls to establish a communications link. A first user interface control requests information from a second user interface control, which then obtains the requested information. The second user interface control then provides the requested information to the first user interface control, and then awaits the validation of the requested information.

Abstract: A multi-act creation user interface element that is displayed when a user instructs a computing system to initiate creation of a resource that has multiple associated creation processing acts. For each of some or all of the creation processing acts, the multi-act creation user interface element causes a set of one or more controls to appear, which the user may then enter creation information into. The multi-step creation user interface element persists creation information so entered so that the creation information is available for further creation processing acts.

Abstract: A user interface that includes a canvas that extends in one direction. An activation mechanism may be used to generate an initial blade in the canvas. A blade is a user interface element that occupies a portion of the canvas in the dimension along which the canvas extends. The blade includes multiple selectable elements that each have a corresponding blade. The user interface includes an extension mechanism configured to present a corresponding subsequent blade on the canvas perhaps adjacent to the prior blade when a selected element from a prior blade is selected, the subsequent blade also including multiple selectable elements that may be hierarchically structured. In this manner, blade chains may be created representative of a journey that the user has taken since initiating the first blade.

Abstract: A user interface that has a canvas that is extendable in an extendable dimension and on which multiple selectable elements may be placed. In this context, when a selecting control is associated with a particular selectable element, and further user gestures are provided, a pan detection mechanism is configured to distinguish between an intent to pan the canvas and an intent to select the particular selectable element. When a selecting control is associated with a particular orthogonally scrollable element, the pan detection mechanism may be distinguish between an intent to pan the canvas and an intent to scroll the orthogonally scrollable element in a direction perpendicular to the extendible dimension of the canvas.

Abstract: A hierarchy of controls and parts, that are each in accordance with constraints of a computing executing context. A control is executable code that performs a function and which may impart a visualization. A part is a unit of visualization container that has its own visualization and/or shows visualizations from one or more compliant controls associated with the part.

Abstract: A query building mechanism in which a query builder component assists a user in generating queries to be used to populate user interface elements. A control provides a query schema to the query builder component. The query schema identifies available query parameters that the control is capable of using to populate a corresponding user interface element. The query builder component presents at least some of the available query parameters the user, such that the user may edit these parameters. The query builder component gathers those edits and generates a query therefrom. The query parameters may be provided to the query builder component in consistent manner across a wide variety of possible user interface controls. Furthermore, the resulting query is provided in a uniform query format.