Microsoft Technology Licensing, LLC

Alvaro Rahul Dias

Brad Olenick

Leon Welicki

Madhur Joshi

Stephen Michael Danton

Vishal R Joshi

Karandeep Singh Anand

Jonah Sterling

Jesse Francisco

William James Staples

Brendyn Alexander

Federico Silva Armas

Jon Harris

Adam Abdelhamed

Kristofer John Owens

Wai Man Yuen

Andrew Birck

Bradley D Millington

Justin Beckwith

Syed Nadir Ahmed

Alaa Shaker

Steven Sanderson

Tom Cox

Nathan J Totten

David Anson

Nafisa Bhojawala

Prabir Krishna Shrestha

Sunay Vaishnav

Marck R Robinson

Christopher Scrosati

Mo Wang

Jonathan R Lucero

Mark David Overholt

Thao Doan

Dina-Marie Ledonna Supino

Andrew Forget

Yu Zhao

Timothy Michael McBride

Jean-Sebastien Goupil

Eric Hwa-Wei Wong

Ryan A Jansen

Ming Chen

Amin Bagheri

Vinela Pothineni

Julio O Casal

Wissam Zeidan

Guruprasad M Airy

Jamey Baumgardt

Guru Kumaraguru

Jean-Sebastien Guopil

Zhao Yu

Julio O Casal Terreros

Dasaradha Ramu Yalamanchili

Julio Casal Terreros

Leon Ezequiel Welicki

Julio 0 Casal Terreros

Jesse David Francisco

Jonah Bush Sterling

Adam Mohamed Abdelhamed

Timothy Michael Mcbride

Techniques are described herein that are capable of virtualizing extension code (e.g., third-party extension code) in an application (e.g., a web application in a browser). A portal of an application is loaded. The portal has an extensibility point via which an extension is to enhance functionality of the application. The extension includes metadata and implementation code. A functionality that the implementation code is configured to provide with regard to the application is automatically determined. The metadata is automatically generated to indicate the functionality in response to the functionality being automatically determined. The metadata is loaded in response to the portal being loaded. Loading of the implementation code is delayed until an interaction indicator is received, in response to loading the metadata. The interaction indicator indicates that a user interaction occurs. The implementation code is loaded based at least in part on receipt of the interaction indicator.

Virtualizing extension code in an application

Computing systems, devices, and associated processes for distributed execution of extensions are disclosed herein. In one embodiment, a method includes receiving a user input at a client device for initiating an extension in a web page associated with a web site. In response to the received user input, a communication link between the client device and a remote computing facility can be established. The method can also include transmitting a request for initiating the extension, from the client device, to the remote computing facility via the established communication link and receiving, at the client device, data representing execution results of the requested extension from the remote computing facility.

Distributed extension execution in computing systems

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.

User interface control and communication

A selection component that facilitates selection of user interface items. Upon receiving a user interface item identification from a data model component, the selection component determines a selection state of the identified user interface item using maintained selection state. The selection component then propagates the selection state in two directions. In one direction, the selection component notifies the identified user interface item of the selection state so that the user interface item may visualize its selection state. In the other direction, the selection component notifies an action module of the selection state of the user interface item so that the action module may take further action external to the user interface item based on the selection state. For instance, the action module might create a new user interface element.

Composable selection model through reusable component

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.

Context aware user interface parts

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.

Service gallery user interface presentation

Techniques are described herein that are capable of virtualizing extension code (e.g., third-party extension code) in an application (e.g., a web application in a browser). A portal of an application that is associated with an extension is loaded. For instance, the portal may have extensibility points to enhance its functionality in a secure manner. The extension includes metadata and implementation code. The metadata is loaded. In response to the portal being loaded, the implementation code may not be loaded until a user interaction occurs.

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.

Generating excutable code from complaint and non-compliant controls

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.

Multi-act creation user interface element

Growing community of inventors

Bellevue, WA, United States of America

Alvaro Rahul Dias