Microsoft Technology Licensing, LLC

Michael J Antonio

Keri D Vandeberghe

Amos Dylan Vance

Christopher Jon Lang

David R Fulmer

John R Schilling

Howard L Cooperstein

David P Relyea

Vivek Bapuji Dalvi

Norm Bryar

Timothy S McGrath

Aiden Byrne

Vlada Knowlton

Julia M Crawford

A method and system for rendering electronic document objects is provided in which a style matrix holds potential attribute values, and attribute references are used to address values in the style matrix. A mix of attribute references and actual attribute values may be used to make some attributes theme- and application-specific, and others theme- and application-independent. Further, a method for rendering a gallery of potential styles is provided. Additionally, a method for associating a style matrix with an electronic document application is provided. Finally, a computer-readable medium for storing a computer-interpretable data structure that identifies a matrix of style attribute types and style attribute values is provided.

Electronic document style matrix

A system and method for utilizing a first managed process to host at least a second managed process is disclosed. The technology initially provides a first managed process. The first managed process hosting at least a second managed process. An unmanaged process is then provided to facilitate communication between the first managed process and the second managed process, such that a user can automatically communicate with the first managed process while the second managed process is operational and the first managed process is in the background without requiring the user to select the first managed process.

Utilizing a first managed process to host at least a second managed process

A location data structure represents a location in a number of different ways, and may include a map view scale appropriate for rending the map. A map view data structure contains sufficient information to derive a number of independent descriptions of a map view. A route data structure may be used at any point in the route calculation and rendering process, and includes a locations field that includes the two-end points of the route, a calculated route data field representing a calculated route between the two end-points, an options field that specifies the options used or to be used to calculate the route, a driving directions field that represents driving directions for the route, and an identity data field that specifies whether the route data structure is a request to calculate a route, a response to a route calculation request, or a rendering request.

Comprehensive mapping data structures and methods for using the same

Growing community of inventors

Seattle, WA, United States of America

Michael J Antonio