Microsoft Technology Licensing, LLC

Michael James Harder

Nikhil Kothari

Andres Sanabria

Vishal R Joshi

Michael Bach

Joseph M Davis

Daniel Philip Chartier

Jon E Jung

Reshmi Mangalore

Anh Thi-Phuong Phan

Jorge E Gabuardi Gonzalez

Simon Calvert

Matthew E Gibbs

Israel Hilerio

Bertrand Le Roy

Eilon J Lipton

Constantin Mihai

Paul Maybee

Scott David Guthrie

Gregory Scott Lindhorst

Shanku Shivabrata Niyogi

Susan Chory

Robert Michael Howard

Ting-Hao Yang

Scott Kirk Imig

Marcelo R Uemura

Joseph Keith Croney

Pravin R Indurkar

David Vincent Reed

Bertrand Claude Le Roy

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.

Selection mapping between fetched files and source files

A selection in a browser in an integrated development environment can be mapped back to the original document that was fetched from a web server by uniquely identifying elements in the original document. A DOM can be created from the original document where the DOM retains the unique identifiers associated with the elements. Block lists for the original document and the DOM can be created. A differencing algorithm can be run on the two block lists. A selection in a browser can be mapped to a location in the DOM block list and the location in the DOM block list can be mapped to the original document.

Mapping selections between a browser and the original fetched file from a web server

A selection in a browser can be mapped back to a corresponding location range in one or more source files that generated the selection. A selection in a source file can be mapped to the corresponding location range in the browser's DOM. The selection in the browser can be mapped to a location range in a block list generated from the DOM. The location range in the DOM's block list can be mapped to a corresponding location range in a block list generated from the fetched file received from a web server. The location range in the fetched file's block list can be mapped to a particular location in the particular source file responsible for generating the selection in the browser. The selection in the browser and the source file can be displayed concurrently, the source file scrolled to the location range corresponding to the selection in the browser.

Live browser tooling in an integrated development environment

Systems and methods that implement interactivity as part of a workflow itself. Data is passed in and out of the workflow to form an interactive workflow, via employing an interactive activity component. Such interactive activity component models suspension points within a workflow definition, wherein user input and associated interaction can be supplied to the workflow during various interactivity breaks that request user input. Such an arrangement enables a controlled/synchronous data exchange between the workflow and a host application associated therewith.

Modeling user input and interaction in workflow based applications

Mapping selections between a browser and the original file fetched from a web server

Various technologies and techniques are disclosed that allow for repurposing content of a source web site for an external web site. The developer uses a programming feature to create a web page with a portion of content suitable for use in the form of a gadget control on an external web site. The developer sets up the portion of the web page for repurposing as the gadget control. When a request is received from the source web site to access the web page, the web page is displayed along with the displayable portion of content in the normal fashion. When a request is received from the external web site to access the portion of content in the form of the gadget control, the portion of content is provided to the external web site for use in the gadget control.

Cross domain presence of web user interface and logic

The described systems and methods are directed at defining web content navigation. The disclosed technique enables the development of web content for a scenario without having to create every navigational control that is needed to manage the flow through the web content in the scenario or to write non-declarative server-side logic to control navigation. This method determines a declaration in a source file for a web page. The declaration is associated with an object. The method determines the views associated with the object where each of the views includes a user-interface. A flow for navigating through the views is determined. The views are rendered in accordance with the navigational flow.

Systems and methods for defining web content navigation

The present invention extends to methods, systems, and computer program products for identifying appropriate client-side script references. Embodiments of the invention facilitate tailoring a list of script references to send to a Web browser based on a list of script references included in a server page. Referenced scripts sent to a Web browser can differ from referenced scripts included in the server page. Script references sent to a Web browser can refer to scripts optimized for the execution environment of the Web browser and to scripts stored at preferred script sources. Further, duplicate script references are removed prior to sending a list of script references to the Web browser. Since script lists sent to Web browsers are tailored for execution environment and duplicates are removed, scripts can be loaded and processed more effectively at Web browsers.

Identifying appropriate client-side script references

The present invention extends to methods, systems, and computer program products for automated generation of different script versions. Received scripts can include comments containing descriptive data from which instructions for implementing specified further functionality (e.g., debugging, testing, tracing, etc.) can be inferred. Received scripts can also include anonymous function names. Modules within a script pre-processor can access the descriptive data and infer instructions for implementing specified further functionality. Modules with the script preprocessor can also infer and assign global identifiers to anonymous functions such that the scripts are subsequently identifiable using the global identifiers. The modules within the script pre-processor can interoperate to generate versions of the script that implement the specified further (e.g., debugging) functionality without requiring a developer to write additional code.

Automated generation of different script versions

The present invention extends to methods, systems, and computer program products for dynamically loading scripts. Web pages can include references to script loaders that control the loading of other scripts at a Web browser. A script loader can load scripts in accordance with script loading rules that override the default script loading behavior of the Web browser. Script loading rules can cause scripts to load in a different order than encountered in a Web pager, load in parallel, load in a manner that limits cross-domain requests, etc. Script loading rules are configurable such at that a developer can create customized script loading behavior.

Dynamically loading scripts

Systems and methods that dynamically reset a workflow state by employing a dynamic state manager that is external to the workflow, and enables interaction of a host with a workflow instance. An event driven workflow or state machine workflow can be supplied, wherein ad hoc events are employed to reset and manipulate the workflow to states that have not been modeled as part of the workflow itself, to dynamically create relation ships at runtime.

Dynamically repositioning workflow by end users

A workflow container defines boundaries within which a user interface appears on a page. The workflow container may change what is displayed on the user interface based on a current state of the workflow. Each workflow container maintains an independent association with a workflow that drives the user interface. The workflow is associated with the workflow container at a control level such that multiple workflows may be independently executed on the same page concurrently or separately.

Control-scoped user interface workflow

In a workflow system data is exchanged using databinding constructs between the workflow and user interface layer. During an execution of a workflow a user interface instance is activated in anticipation of a user input event. The workflow is suspended and data for populating the user interface instance is provided to the user interface layer using a databinding construct from the workflow. Upon receiving user input, another instance of the workflow is loaded and data associated with the user input provided from the user interface to the workflow employing a databinding construct such that the other instance of the workflow is executed with the data associated with the user input.

Growing community of inventors

Bellevue, WA, United States of America

Michael James Harder