Microsoft Technology Licensing, LLC

Other

Mikhail Arkhipov

Vishal R Joshi

Wai Man Yuen

Justin Beckwith

Alex Mogilevsky

Mark Douglas Harper

Abhijit Rao

Charles Bissonnette

Wai Hang Tang

Thao Doan

Alison Q Lu

Li Zhang

C Douglas Hodges

Evgeny Veselov

Elliot H Omiya

Gregg Bernard Miskelly

Joseph M Davis

Sam Spencer

Joshua I Kaplan

Gregg B Miskelly

Timothy Michael Mc Bride

Systems and methods are described for providing code completion features for code modules that have been incorporated into a source code document being edited by a user of a source code editor. Embodiment dynamically load and apply partial code evaluation to code modules referenced in the source code document (and any code modules referenced directly or indirectly by such code modules) while the user is editing it. The partial code evaluation is performed on a background thread that is separate from a main thread used to execute the user interface for the source code editor. The results of such partial code evaluation are cached and used to provide code completion information for the code modules.

System and method for providing code completion features for code modules

Systems and methods for providing auto-completion functionality in a source code editor are described. In accordance with the systems and methods, code entities that are candidates for auto-completion are presented to a user via multiple auto-completion menus that are accessed in steps rather than via a single auto-completion menu. The multiple auto-completion menus include at least a first menu and a second menu. The first menu includes a common portion (e.g., a common prefix) of a subset of the candidate code entities. The second menu includes the subset of the candidate code entities and is presented when the user selects the common portion from the first menu.

Multi-step auto-completion model for software development environments

Systems and methods perform asynchronous error checking on a structured document. In accordance with the systems/methods, a first thread, such as a main application thread of a document editor, parses the document to identify one or more new elements included therein and create copies of the one or more new elements. A second thread, such as a background thread, applies error checking to the copies of the one or more new elements to generate error results corresponding to the one or more new elements. The first thread the uses the error results to indicate errors in association with the one or more new elements.

Asynchronous error checking in structured documents

Techniques are described herein that are capable of incrementally tokenizing and/or parsing a style sheet. For example, tokens may be created to represent respective sequences of characters in a style sheet. A token that includes a change (a.k.a. a changed token) and other token(s) that follow the changed token may be re-tokenized and/or parsed without re-tokenizing and/or parsing token(s) that precede the changed token. In another example, hierarchical node trees may be used to represent a style sheet. Each of the hierarchical node trees includes a respective subset of tokens, which are assigned among various hierarchical levels of the respective hierarchical node tree. Each of the tokens has a respective absolute or relative character position that indicates a location in the style sheet of the sequence of characters that is represented by the respective token. Absolute character positions may be updated without updating the relative character positions.

Incrementally tokenizing and/or parsing a style sheet

The present invention extends to methods, systems, and computer program products for mapping breakpoints between Web based documents. Embodiments of the invention facilitate extracting corresponding client script blocks from different Web based documents to disassociate the client script blocks with their relative locations within the Web based documents. From the extracted client side script blocks, a position for mapping a breakpoint from one client side script block another client side script block can be determined. The breakpoint is then copied from the one client script block and inserted into the determined position in the other client script block. The client script blocks can then be re-associated with their relative locations in the Web based documents from which they were extracted.

Mapping breakpoints between web based documents

A proxy service for simulating real assembly features on a remote device is described. A data stream including reflection data of a real assembly is generated. The reflection data stream may include data associated with proxy types without including the code from the real assembly. A client obtains the reflection data stream. The reflection data stream facilitates the generation of a proxy assembly on the client and allows the client to instantiate features of the real assembly on the client without the code for the real assembly.

Proxy assembly for simulating real assembly features on a remote device

The present invention extends to methods, systems, and computer program products for synchronizing data between different editor views. Embodiments of the present invention can be used to incrementally parse a portion of a document using a mark-up language (e.g., HTML) snippet. The parsed snippet is then merged back into the main document. Accordingly, code changes in a text view can be integrated into a design view's main document structure (e.g., parse tree) such that the preservation information for the parsed snippet is merged with the preservation information for the rest of the document. Fully reparsing the document is not required and incremental reparsing can be done in automated fashion. Thus, a document can be automatically re-outputted with full preservation of what the document would have looked like in code view without fully reparsing the document.

Synchronizing data between different editor views

The present invention extends to methods, systems, and computer program products for synchronizing undo/redo operations between different document views. A unified undo stack uniformly stores undo operations and information for multiple views of a document. When a change in first view is detected, the first view submits an undo unit for storage in a global undo unit in the unified undo stack. A second view is notified of the detected change in the first view. In response, the second view submits an undo unit for storage in the global undo unit. Accordingly, undo information for both views is stored together at the unified undo stack. When an undo command is receive from either view, appropriate undo units for each view are applied to each view respectively.

Synchronizing undo/redo operations between different document views

A user interface event is received by way of a user interface. A software component adapted to process the user interface event may be pushed onto a memory stack, and the user interface event may be processed using the software component on the stack, or with a software component that is not on the stack. The software component on the stack, if used, may then be popped from the memory stack. In addition, a plurality of software components may be pushed onto the memory stack, and in that case, at least one of the components may be selected to process the user interface event. The user interface event is processed using at least one of the plurality of software components, and one or more of the plurality of software components are popped from the memory stack.

Configurable event handling for user interface components

An API and method for processing a user interface event is provided. The user interface event may take place in any environment of a software application, and may result from any type of user or software action. An embodiment also provides a framework for customizing the processing of a user interface event without the need to maintain accountability of computer states. In the method, an application process user interface event is processed using an operating system process. A user interface event is received by the application process by way of a user interface. A software component adapted to process the user interface event is pushed onto a memory stack by the operating system process. The operating system process processes the user interface event using the software component, and pops the software component from the memory stack.

Configurable event handling for an interactive design environment

A source code editor is used to develop multilanguage documents while providing the advanced editing functionality of secondary editors and without requiring the programmer to explicitly open and interface with the secondary editors. The multilanguage document is presented to the user in a primary application view of the primary editor. Code segments written in different languages are identified and sent to the appropriate secondary editors, which in turn create secondary documents that are transparent to the programmer. As edits are made to the primary application view of the document, the edits are replicated by the secondary editors behind the scene. Functionality that is enabled by the secondary editors, such as syntax coloring, auto-completion, and validation is identified by the primary editor and replicated in the primary application view, so as to appear as if the primary editor is inherently configured with the leveraged functionality of the secondary editors.

Growing community of inventors

Woodinville, WA, United States of America

Mikhail Arkhipov