Microsoft Technology Licensing, LLC

Jonathan Ian Gordner

Jesse Clay Satterfield

Navjot Singh

Paula Guntaur

Marina Dukhon

Amy Elizabeth Alberts

Maria Fernandez Trevino

Ethan Joseph Bernstein

Jonathan Bailor

Kelly Michael Krout

Matthew Eric Mizulo

Chaitanya Dev Sareen

Stephan Hoefnagels

Mirko Mandic

Kieran Snyder

Roger H Wynn

Brian Eric Uphoff

Josh A Clow

Brendan D Elliott

Richie Fang

Sivaramakrishna Mopati

Nandini Bhattacharya

Colin Jeanne

Alexander Allen

Wenjun Wang

Kenneth Parker

Yadriel Gonzalez Perez

Jonathan Li

An out-space actuator is selected to access an out-space user interface for a document editor program. An out-space actuator is associated with an in-space user interface having a displayed document. When the out-space actuator is selected, an out-space user interface is displayed that includes an expanded feature selection surface. The out-space user interface may be used to display one or more status panes for providing status information about a document being edited in the in-space user interface. Application features for affecting changes to a given document's status may be exposed in the out-space interface in proximity to associated status information. An out-space communication user interface (UI) component may be temporarily displayed in the document in-space user interface to communicate document status information that is presently available in the out-space user interface. A message bar may be displayed in the in-space user interface for communicating information from the out-space user interface.

Transitions between user interfaces in a content editing application

Architecture that generates a companion window in combination with a source application experience to enable the accomplishment of a side task yet not switch away from the context of the source application. The companion window experience is a window that is rendered proximate (e.g., beside) a user's source application experience, in a predictable location, and with a predictable user model for invocation and dismissal. The companion window allows the user to retain full visual context of the associated source application experience, while rendering activities that directly pertain to the source application experience or activities that allow the user to interact with two applications.

Companion window experience

One or more techniques and/or systems are provided for implementing a reverse protocol launch. For example, the reverse protocol launch may be implemented between apps (e.g., as an app-to-app protocol) such that a user may navigate between apps in a contextually relevant manner using the reverse protocol launch. In an example, a search app may display vacation search results based upon a search query. Responsive to a selection of a vacation movie search result, a transition to a movie app may occur. A context, specifying a contextual state of the search app (e.g., information regarding the vacation search results, the search query, etc.), may be sent to the movie app. The movie app may implement a reverse protocol launch using the context to transition from the movie app back to the search app in the contextual state (e.g., the search app may be repopulated with the vacation search results, etc.).

Reverse launch protocol

Embodiments of a collaborative authoring environment enable a user to resolve editing conflicts arising when synchronizing a user copy of a data file with a master copy of the data file. Content updates may be synchronized separately from metadata updates. Metadata updates may be synchronized automatically, whereas content updates may be synchronized only when any identified editing conflicts are resolved. When an editing conflict is identified, the user interface of the authoring application may be configured to toggle between displaying and hiding the identified editing conflicts.

Conflict resolution

Communication between a document editor in-space user interface and a document editor out-space user interface

In embodiments of identifying search matches and altered search results, a query is received from a device application, and a data search is initiated based on the query that specifies search terms. A search result set of search result items is then received, and properties of a search result item are correlated with the search result item, where the properties indicate why the search result item was returned as part of the search result set. Search terms of the query are also associated with respective properties of the search result item to indicate a correspondence of a search term with a property of the search result item. The search result set of the search result items can then be returned to the device application along with the properties of each search result item and the associated search terms of the query.

Identifying search matches and altered search results

Growing community of inventors

Seattle, WA, United States of America

Jonathan Ian Gordner