Microsoft Technology Licensing, LLC

Kai-Uwe Maetzel

Daniel John Imms

Peng Lyu

Hui Ling Er

Some embodiments provide a notebook tool enhanced with minimoremap functionality. Notebooks are multicell documents with varied mime types present in the content of various cells of a given notebook, including executable source code such as scripts, non-executable content, markdown text, natural language text, photos, videos, maps, and more. The notebook tool includes a main view and a superimposed minimoremap view which is functionally coordinated with the main view, e.g., for navigation and cell selection. Notebook cell operations are commanded via the minimoremap. Cells outside the main view viewport are modified without changing the user interface main view focus. Tool-human interaction commands cause the performance of notebook operations such as cell execution, cell rearrangement, cell collapse, cells merge, cells grouping, or cell dependency analysis. Minimoremap cell images are rendered as icons, as graphics, or as scaled-down versions of previously rendered full-size main view images.

Multicell document editor minimoremap

Some embodiments transfer a software development working context between development environments. The environments may be on the same machine, or on different machines. The working context includes ephemeral state information (ESI), such as edits not yet committed to a repository, development tool user interface state, command history, build history, debug history, execution history, tool window content, hot exit files, or search filters, among others. The ESI is computationally gathered from RAM and other locations in a source environment, written to an edit session artifact (ESA), and then read from the ESA and installed at a target environment. The transfer is accomplished without committing source code to any source code version control system, e.g., repository. The transfer may be tailored for efficiency or efficacy by determining whether a particular software development capability is present in one or both of the environments.

Working context transfer across development environments

Switching shells attached to a terminal. Suppose that a shell has already output text into the terminal, and at that point a new shell is to be attached to the terminal. That subsequent shell is then started up, and text output is gathered from that new shell. Content representing that new shell is then displayed in the terminal. As an example, if the output is the same for the new shell as it was for the old shell, the terminal can just keep the old output displayed in the terminal, and eliminate the need to also output the identical output from the new shell. If the output of the new shell is different than that of the old shell, the terminal may be refreshed and the new content rendered perhaps in a single frame and/or without displaying text associated with this switching activity.

Growing community of inventors

Seattle, WA, United States of America

Kai-Uwe Maetzel