Microsoft Technology Licensing, LLC

Kevin Michael Babbitt

Tony Edward Schreiner

Bradley Joseph Litterell

Matthew Allen Rakow

Praveen Kumar Muralidhar Rao

Wissam S Kazan

Daniel Gwozdz

Felipe Luis Naranjo

Russell Scott Randall

Rossen Atanassov

Bogdan Brinza

Justin Rogers

Christian Fortini

Richard Keith James

Samuel R Fortiner

Arron J Eicholz

Sylvain Pierre Galineau

Ian J Prest

A system described herein includes a receiver component that receives an indication that a user has selected a first selectable buttontab in a toolbar installed in a client application. The system further includes a display component that causes a dashboard to be displayed on a display device in response to receipt of the indication that the user has selected the buttontab. The dashboard includes a content window that displays content and the buttontab, wherein the dashboard is a seamless visual combination of the buttontab and the content window.

Toolbar dashboard functionality

In one embodiment, a change to a format of user interface output being output in a user interface is received. Relationships between nodes in a document object model and rules in a style specification are analyzed to determine a context of the change with respect to first nodes in the document object model. The context indicates the change affects a format of the first nodes. Second nodes in the document object model that are associated with the cascade are identified based on the context. The cascade is applied to the second nodes and the first nodes by calculating the change in the format of the user interface output for the second nodes and the first nodes.

Context aware cascade operations

A first thread receives a start movement command and a parametric curve from a second thread in response to the second thread receiving an input to move an element that is rendered in an interface. The parametric curve defines parameters for movement of an element. The first thread calculates a positioning of the element on the interface using the parametric curve. Then, the first thread positions the element in the interface based on the positioning and continues to calculate the positioning and position the element in the interface using the parametric curve until a stop movement command is received from the second thread.

Thread independent parametric positioning for rendering elements

A first thread sends a rendering request for a scalable video graphics operation using a scalable video graphics object to a second thread. The second thread processes the scalable video graphics operation to render the scalable video graphics object using a first set of parameters that is stored in a data structure. The first thread performs a computation that calculates a second set of parameters for the scalable video graphics operation and stores the second set of parameters in the data structure. The first thread sends a signal to the second thread indicating that the first set of parameters have changed to the second set of parameters to allow the second thread to synchronize and use the second set of parameters to process the scalable video graphics operation.

Thread independent scalable vector graphics operations

In at least some embodiments, a mechanism is provided for web developers to request specific default behaviors, such as touch behaviors, on their webpages. In at least some implementations, a Cascading Style Sheets (CSS) rule is utilized to enable or disable manipulations such as panning, pinch zoom, and double-tap-zoom manipulations. The mechanism can be extensible to accommodate additional default behaviors that are added in the future. In various embodiments, the behaviors are declared up front and thus differ from solutions which employ an imperative model. The declarative nature of this approach allows achievement of full independence from the main thread and deciding the correct response using independent hit testing.

Declarative style rules for default touch behaviors

In one or more embodiments, a hit test thread which is separate from the main thread, e.g. the user interface thread, is utilized for hit testing on web content. Using a separate thread for hit testing can allow targets to be quickly ascertained. In cases where the appropriate response is handled by a separate thread, such as a manipulation thread that can be used for touch manipulations such as panning and pinch zooming, manipulation can occur without blocking on the main thread. This results in the response time that is consistently quick even on low-end hardware over a variety of scenarios.

Independent hit testing

In at least some embodiments, a mechanism is provided for web developers to request specific default behaviors, such as touch behaviors, on their webpages. In at least some implementations, a Cascading Style Sheets (CSS) rule is utilized to enable or disable manipulations such as panning, pinch zoom, and double-tap-zoom manipulations. The mechanism can be extensible to accommodate additional default behaviors that are added in the future. In various embodiments, the behaviors are declared upfront and thus differ from solutions which employ an imperative model. The declarative nature of this approach allows achievement of full independence from the main thread and deciding the correct response using independent hit testing.

Growing community of inventors

Sammamish, WA, United States of America

Kevin Michael Babbitt