Inline display and preview of related information for elements in a document

• US 10,331,289 B2
• Filed: 11/17/2015
• Issued: 06/25/2019
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hammontree, Monty, Hosabettu Kamalesha, Murali Krishna, Adams, Brandon, Clarke, Steven John, Tkachenko, Oleg, Zaiss, Zachary S, Tilford, John, Pugh, David, Dole, Daniel
• Primary Examiner(s): Rivera, Anibal
• Application Number:
  US14/944,162
• Publication Number:
  US 20160070422A1
• Time in Patent Office: 1,316 Days
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/04855 Interaction with scrollbars
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting
• CPC Class Codes: G06F 8/33 Intelligent editors
• CPC Class Codes: G06F 8/34 Graphical or visual programming

Abstract

Disclosed herein is a system and method for optimizing a developer'"'"'s ability to find and navigate relevant documents, relationships, and other information related to an identifier in the code they are developing. An inline viewport is presented to the user in response to the user selecting an identifier in the code whereby the user is able to see relevant information related to the identifier in a spatially consistent location with the code they are investigating. Further, the developer has the ability to make changes to the code in the viewport without leaving the current editor.

Claims

1. A method comprising:

associating a plurality of relationship types with an identifier in a portion of code being displayed in a graphical user interface (GUI) of a code editor, each relationship type of the plurality of relationship types being selected from a predefined set of relationship types, each relationship type in the predefined set of relationship types describing a different manner in which the identifier relates to another code construct;

presenting in the GUI a list of the plurality of relationship types associated with the identifier;

receiving an indication of a selection of a first relationship type in the plurality of relationship types;

accessing a first document associated with the selected first relationship type;

opening a viewport in the portion of code that is being displayed in the GUI, the viewport displacing at least a second portion of the code that is being displayed in the GUI;

displaying at least a portion of the first document in the viewport;

receiving an indication of a selection of a second relationship type in the plurality of relationship types;

accessing a second document associated with the selected second relationship type;

displaying at least a portion of the second document in the viewport in place of the at least a portion of the first document; and

providing a user interface element that when interacted with causes the at least a portion of the first document to be redisplayed in the viewport.

2. The method of claim 1 further comprising:

receiving an indication from a user that a portion of text in the portion of the code is the identifier.

3. The method of claim 1 wherein associating the plurality of relationship types further comprises:

passing the identifier to at least one provider; and

receiving from the at least one provider an indication that the at least one provider has a document related to the identifier.

4. The method of claim 1 wherein displaying at least a portion of the first document in the viewport comprises:

identifying an entity of interest in the first document; and

displaying the entity of interest in the viewport.

5. The method of claim 4 wherein displaying the entity of interest further comprises:

displaying the entity of interest differently from a portion of the first document that is not part of the entity of interest.

6. The method of claim 1 further comprising:

determining a second identifier in the first document displayed in the viewport;

associating a second plurality of relationship types for the second identifier;

receiving an indication of a selection of a third relationship type in the second plurality of relationship types;

accessing a third document associated with the selected third relationship type; and

displaying the third document in the viewport.

7. The method of claim 6 wherein displaying the third document in the viewport comprises:

opening a second viewport in the portion of code.

8. The method of claim 1 wherein opening the viewport in the portion of the code further comprises:

creating a visual break point in the portion of the code at a location of the identifier; and

inserting the viewport in a space between the location and the second portion of the code.

9. The method of claim 1 further comprising:

instantiating an embedded editor in the viewport.

10. A system having at least one processor for inserting a viewport into a portion of code being displayed in a graphical user interface (GUI) of a code editor, comprising:

a peek command module configured to determine a request for a plurality of relationship types for an identifier in the portion of code being displayed in the GUI, each relationship type of the plurality of relationship types being selected from a predefined set of relationship types, each relationship type in the predefined set of relationship types describing a different manner in which the identifier relates to another code construct;

a broker configured to determine the plurality of relationship types for the identifier received from the peek command module, and to request a first document associated with a first relationship type in the plurality of relationship types and a second document associated with a second relationship type in the plurality of relationship types; and

at least one provider configured to provide at least the first relationship type and the second relationship type to the broker in response to a request from the broker for the plurality of relationship types;

a viewport controller module configured to create a viewport in the portion of the code that is being displayed in the GUI by;

inserting at least a portion of the first document into the portion of code; and

subsequent to inserting the at least a portion of the first document into the portion of code, replacing the at least a portion of the first document with at least a portion of the second document; and

providing a user interface element that when interacted with causes the at least a portion of the first document to be reinserted into the portion of code.

11. The system of claim 10 wherein the peek command module is further configured to determine a selection of the first relationship type in the plurality of relationship types and to request the first document associated with the selected first relationship type.

12. The system of claim 10 wherein the viewport controller module is further configured to create a second viewport in the portion of the code.

13. The system of claim 10 wherein the viewport controller module is further configured to modify the first document such that an entity of interest in the first document is displayed differently from a portion of the first document that is not part of the entity of interest.

14. The system of claim 10 wherein the viewport controller module is further configured to:

determine a location of the identifier in the portion of the code; and

insert the viewport below the location by moving a second portion of the portion of the code to a second location such that the viewport is disposed between the location and the second location.

15. The system of claim 10 wherein the viewport controller module is further configured to maintain a history of documents that have been inserted into the code through the viewport.

16. A method comprising:

determining an identifier in a portion of code being displayed in a graphical user interface (GUI) of a code editor;

associating a plurality of relationship types with the identifier, each relationship type of the plurality of relationship types being selected from a predefined set of relationship types, each relationship type in the predefined set of relationship types describing a different manner in which the identifier relates to another code construct;

presenting in the GUI a list of the plurality of relationship types;

receiving an indication of a selection of a first relationship type in the plurality of relationship types;

accessing a first document associated with the selected first relationship type;

opening at least a portion of the first document in a viewport in the portion of code that is being displayed in the GUI;

adding the at least a portion of the first document to a history of actions;

receiving an indication of a selection of a second relationship type in the plurality of relationship types;

accessing a second document associated with the selected second relationship type;

opening at least a portion of the second document in the viewport in place of the at least a portion of the first document;

adding the at least a portion of the second document to the history of actions; and

providing a user interface element that when interacted with causes the redisplay of the at least a portion of the first document in the viewport.

17. The method of claim 16 further comprising:

displaying the history of actions with the viewport.

18. The method of claim 17 further comprising:

navigating to a different document in the history of actions through the displayed history of actions through the displayed history of actions.

19. The method of claim 16 further comprising:

interacting with the at least the portion of the first document in the viewport.

20. The method of claim 16 further comprising:

determining a second identifier in the first document displayed in the viewport;

associating a second plurality of relationship types with the second identifier;

receiving an indication of a selection of a third relationship type in the second plurality of relationship types;

accessing a third document associated with the third selected relationship type;

opening at least a portion of the third document in the viewport; and

adding the at least a portion of the third document to the history of action.