Abstract: An element in a fetched file (a file received from the web server in response to an HTTP request) can be mapped to the source code that generated it and vice versa. When code is compiled at the web server, calls can be executed that emit HTML that includes metadata that maps a snippet of code back to a particular source file and to a particular location in the source file. The HTML can include injected symbols that specify that the information from a particular start position for a particular character length in the HTML comes from a particular start position to a particular end position in the source file.

Abstract: Systems and methods for providing auto-completion functionality in a source code editor are described. In accordance with the systems and methods, code entities that are candidates for auto-completion are presented to a user via multiple auto-completion menus that are accessed in steps rather than via a single auto-completion menu. The multiple auto-completion menus include at least a first menu and a second menu. The first menu includes a common portion (e.g., a common prefix) of a subset of the candidate code entities. The second menu includes the subset of the candidate code entities and is presented when the user selects the common portion from the first menu.

Abstract: Systems and methods for providing auto-completion functionality in a source code editor are described. In accordance with the systems and methods, code entities that are candidates for auto-completion are presented to a user via multiple auto-completion menus that are accessed in steps rather than via a single auto-completion menu. The multiple auto-completion menus include at least a first menu and a second menu. The first menu includes a common portion (e.g., a common prefix) of a subset of the candidate code entities. The second menu includes the subset of the candidate code entities and is presented when the user selects the common portion from the first menu.

Abstract: A method of provisioning a Web hosting resource includes providing a cloud service. A request for a Web hosting resource is received by the cloud service, wherein the request is provided by a client. The cloud service identifies a Web host based on the received request for a Web hosting resource. The cloud service sends a request to the Web host to provision a first Web hosting resource for use by the client.

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 method of provisioning a Web hosting resource includes providing a cloud service. A request for a Web hosting resource is received by the cloud service, wherein the request is provided by a client. The cloud service identifies a Web host based on the received request for a Web hosting resource. The cloud service sends a request to the Web host to provision a first Web hosting resource for use by the client.

Abstract: Computing systems in which multiple non-context-sensitive or core commands may be initiated from each of a number of different user interface contexts. There are also multiple context-sensitive mechanism for visualizing the commands depending on which of the multiple possible user interface contexts that the commands appear. At least some embodiments described herein also related to the presentation of dialogs at various stages of the command lifecycle without the system needing to know the underlying operations of the command, and allowing the developer to specify when dialogs are to appear in that lifecycle.

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 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: Dialogs within a user interface. The user interface has one or more selectable elements, the selection of each of which initiating a corresponding action. Each time that any of the elements is selected, and a corresponding action initiated, there is the potential for the user interface to display a dialog associated with the initiated action. The dialogs are displayed so as to be positioned with respect to the element whose selection caused the corresponding action to be initiated.

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 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 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.

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 development tool is described herein. The development tool automatically identifies one or more resources associated with a first version of a Web site that is being developed by a user of the tool. The development tool also automatically interacts with at least one entity within a Web hosting environment to cause a companion resource to be provisioned in the Web hosting environment for each local resource so identified. The development tool may also automatically interact with at least one entity within the Web hosting environment to properly configure a published version of the Web site to utilize at least one companion resource.

Abstract: Systems and methods for providing auto-completion functionality in a source code editor are described. In accordance with the systems and methods, code entities that are candidates for auto-completion are presented to a user via multiple auto-completion menus that are accessed in steps rather than via a single auto-completion menu. The multiple auto-completion menus include at least a first menu and a second menu. The first menu includes a common portion (e.g., a common prefix) of a subset of the candidate code entities. The second menu includes the subset of the candidate code entities and is presented when the user selects the common portion from the first menu.

Abstract: Systems and methods are described for providing code completion features for code modules that have been incorporated into a source code document being edited by a user of a source code editor. Embodiment dynamically load and apply partial code evaluation to code modules referenced in the source code document (and any code modules referenced directly or indirectly by such code modules) while the user is editing it. The partial code evaluation is performed on a background thread that is separate from a main thread used to execute the user interface for the source code editor. The results of such partial code evaluation are cached and used to provide code completion information for the code modules.

Abstract: A developer is enabled to select a website for editing. The website is defined by a plurality of files stored at a server. The website files stored at the server include files containing code and may optionally include one or more un-editable files. In response to the developer selecting the website for editing, a call is issued to download a copy of the files containing code from the server to store in a cache at the computing device. The developer is enabled to edit the files containing code to generate an edited version of the website, including being enabled to edit a downloaded copy of a file containing code in the cache when a copy of at least one other file containing code has not yet been downloaded to the cache in response to the call. The developer is enabled to display the edited version of the website.

Abstract: Aspects of the subject matter described herein relate to publishing applications from a source environment to a target environment. In aspects, a publishing pipeline has multiple segments in which work related to the publishing is performed. In the pipeline, file data associated with an application is collected. Settings that need to be created and/or changed in target environment are also determined. Transformation actions may also occur to determine and prepare files to be published to the target environment. After the files and settings to publish are determined and the transformation actions occur, the application may then be published to the target environment.