Microsoft Technology Licensing, LLC

Robert Anthony DeLine

Steven Mark Drucker

Mike Barnett

John Carlton Platt

Jonathan David Goldstein

Danyel Aharon Fisher

Badrish Chandramouli

George G Robertson

Mary P Czerwinski

Manuel Alfred Fahndrich

Andrew Craig Bragdon

Kael R Rowan

Brian R Meyers

Nikolai Tillmann

Gina Danielle Venolia

Meredith June Morris

Shaz Qadeer

Jens K Jacobsen

Ken Hinckley

Akash Lal

Jonathan De Halleux

The described implementations relate to processing of electronic data. One implementation is manifest as a technique that can include obtaining a relational query that references one or more data items and associating progress intervals with the data items. The technique can also include converting the relational query into a corresponding streaming query, and providing the streaming query and the data items with the progress intervals to a stream engine that produces incremental results of the query. For example, the progress intervals can be based on row numbers of a relational database table. The progress intervals can be used to define event lifetimes of streaming events that are provided as inputs to the stream engine.

Progressive query computation using streaming architectures

Information sharing between meeting attendees during a co-located group meeting in a meeting space is democratized using a computer that is operating cooperatively with one or more object sensing devices in the meeting space to identify postures formed by the meeting attendees.

Information sharing democratization for co-located group meetings

Various technologies pertaining to answering reachability queries are described herein. A reachability query includes a user-specified destination line of code in source code that is desirably analyzed. A theorem prover is employed to identify an execution path through the source code that reaches the destination line of code. Graphical data is presented to the user that illustrates to the user the execution path through the source code that reaches the destination line of code.

Identifying execution paths that satisfy reachability queries

A debugger session is initiated to monitor application execution. A debugger canvas corresponding to the debugger session is identified and displayed. The displayed debugger canvas includes one or more code bubbles created during a prior debugger session. The one or more code bubbles already present on the displayed debugger canvas are reused during the current debugger session. Accordingly, existing code bubbles and bubble sets are reused on a debugger canvas when entering a debug session, thus providing a more stable and manageable view for debugging an application in an integrated development environment. The code fragments in code bubbles on a debugger canvas can be analyzed, inspected, and edited during or after a debug session. Notations can also be added to a debugger canvas in the form of note bubbles and context data bubbles.

Debugging code visually on a canvas

The present disclosure describes an apparatus and a method for contemporaneously viewing code structure in a diagram as well as source code facilitated by a semantic zoom and pan feature and enabled via use of advanced rendering engines. The apparatus and method support in-place editing where edits are represented on the diagram in real-time. One example system includes a diagramming surface, an advanced rendering engine, viewers with controls and data retrieval modules, a data store with data loaded from source code well as external sources, and workers possibly implemented as background threads to monitor changes. One example method enables layers where a subset of data is viewed and a corresponding control is used to manipulate the data. An advanced rendering engine enables a wide range of user interface techniques, including but not limited to semantic zoom and pan and in-place editing.

Source code semantic zoom and spatial layout

Described herein are interactive graphical user interfaces that visualize execution behavior of source code together with theoretical execution behavior of the source code together with the source code itself. Structure of the source code is analyzed to determine theoretical execution behavior of the source code. Thereafter, symbolic execution of the source code is undertaken to output an execution trace. The execution trace is shown together with the theoretical execution behavior of the source code.

Graphical user interface for exploring source code execution behavior

A method and system for tracking and processing user interaction information from multiple computing devices. Individual computing devices collect user interaction information corresponding to user interaction with discrete units of a set of data, such as software programming code. The individual information is collected and processed to generate a cumulative set of user interaction information that is transmitted back to the client computing devices. The client computing devices can then provide various visual interfaces corresponding to the processed user interaction data.

System and method for managing user interaction data in a networked environment

A 'Spatial Navigator' provides a document navigation environment that leverages user spatial memory. Graphical thumbnail-type representations ('thumbnails') provide scaled versions of entire documents. Changes to documents are immediately reflected in corresponding thumbnails. Similarly, document search results are highlighted in corresponding thumbnails. One or more dynamic document selection windows present arrangements of a plurality of these thumbnails for user selection and interaction. Each dynamic document selection window provides real-time inter-file navigation by allowing user selection and opening of documents, or any location or portion of a document, through user interaction with the corresponding thumbnail. Once a document is opened, intra-file navigation is enhanced by providing another scaled version of the entire document in a dynamic scrollbar adjacent to a primary document editing/viewing window. Selection of any point within this scrollbar-based thumbnail causes an immediate jump to the corresponding document location in the primary document editing/viewing window.

Dynamic thumbnails for document navigation

A software program can be represented as a map depicting respective software components of the software program. A grid system can be used, and map elements can be contiguous geometric shapes. Affinity between the software components can be represented in the map, such as by placing corresponding map elements close to one other in the map. During navigation through source code, an indication of where within the source code the navigation has occurred can be displayed on the map. Paths can be shown on the map. A technique for building the map can rely on a metric of a software component when generating a corresponding map element in the software map. The map can be depicted as a geographic map to help developers locate components.

Cartographic software maps

A system and method employing pre- and/or post-condition(s) specified at a source code level and persisted (e.g., in associated object code and/or a specification repository) facilitating static checking of the object code is provided. The system and method are based, at least in part, upon a framework that employs rules for using an interface to be recorded as declarative specifications in an existing language. A specifier can give a method a plug-in pre- and postcondition, which is arbitrary code that examines an object's current state and a static approximation of the method's actuals, decides whether the call is legal and returns the object's state after the call.

Plug-in pre- and postconditions for static program analysis

A system and method employing pre- and/or post-condition(s) specified at a source code level and persisted (e.g., in associated object code and/or a specification repository) facilitating static checking of the object code is provided. The system and method are based, at least in part, upon a framework that employs rules for using an interface to be recorded as declarative specifications in an existing language. The system can employ a range of annotations that allow a developer to specify interface rule(s) with varying precision. At the simplest end of the range, a specifier can mark those methods that allocate and release resource(s). A specifier can also limit the order in which an object's methods may be called to the transitions of a finite state machine. At the more complex end of the range, a specifier can give a method a plug-in pre- and post condition, which is arbitrary code that examines an object's current state and a static approximation of the method's actuals, decides whether the call is legal and returns the object's state after the call.

Growing community of inventors

Seattle, WA, United States of America

Robert Anthony DeLine