Inline display and preview of related information for elements in a document
US-2016070422-A1 · Mar 10, 2016 · US
US9785302B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9785302-B2 |
| Application number | US-201313907850-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 31, 2013 |
| Priority date | Mar 14, 2013 |
| Publication date | Oct 10, 2017 |
| Grant date | Oct 10, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
The invention claimed is: 1. A system comprising: at least one processor; a memory; a user interface configured to display at least a portion of a code; an editor configured to allow a user to interact with the code displayed on the user interface, the editor comprising: a peek command module configured to display to the user at least one identifier in the at least a portion of the code indicating that the at least one identifier participates in at least one relationship with an entity of interest in a document separate from the code; and a viewport controller module configured to create a viewport in the code in response to the user selecting the at least one identifier in the code, to display the entity of interest within the viewport such that the user views at least a portion of the entity of interest from within the displayed code, and to display a history indicator to indicate at least one entity previously displayed within the viewport, the history indicator including a reference to a launch point in at least one of the code or the document and a landing point in at least one of the code or the document. 2. The system of claim 1 further comprising: a broker configured to receive from the peek command module a request for the at least one relationship that the at least one identifier participates in, and is further configured to provide to the viewport controller module the at least one relationship that is available for the requested identifier. 3. The system of claim 2 wherein the broker is further configured to receive from the peek command module an indication of a selection of the at least one relationship and to provide to the viewport controller module the entity of interest associated with the at least one relationship. 4. The system of claim 2 further comprising: at least one provider configured to: receive from the broker the request; determine if the at least one provider has a document that includes an entity of interest that is related to the at least one identifier; and provide the broker with information related to the entity of interest in the document when the document is determined to be related to the at least one identifier. 5. The system of claim 4 wherein the at least one provider provides the broker with the entity of interest when the document is determined to be related to the at least one identifier. 6. The system of claim 1 wherein the viewport controller module is configured to cause only a portion of the entity of interest to be displayed in the viewport. 7. The system of claim 1 wherein the entity of interest comprises a portion of a document. 8. The system of claim 7 wherein the viewport is sized such that only a first portion of the document is displayed in the viewport and wherein a remainder of the document is displayed in the viewport when the user navigates to a second portion of the document that is not initially displayed in the viewport. 9. The system of claim 8 wherein the viewport controller module is further configured to cause the entity of interest to be displayed in the viewport in a format different from a format used to display the document, such that the user can determine when the user has navigated to a portion of the document that is outside the entity of interest. 10. The system of claim 1 wherein the editor further comprises: an embedded editor configured to permit the user to edit the entity of interest displayed in the viewport from within the viewport. 11. A method of interacting with code in an integrated design environment comprising: displaying at least a portion of the code in a user interface; indicating in the at least a portion of the code at least one identifier; receiving an indication that a user has selected the at least one identifier; presenting a set of relationships associated with the selected at least one identifier on the user interface; receiving a selection of at least one of the set of relationships; retrieving a document associated with the selected relationship; opening an inline view in the code; and displaying at least a portion of the document and a history indicator to indicate at least one entity previously displayed within the viewport in the inline view, the history indicator including a reference to a launch point in at least one of the code or the document and a landing point in at least one of the code or the document. 12. The method of claim 11 wherein the at least a portion of the document includes an entity of interest. 13. The method of claim 12 wherein the inline view is sized so as to display only a first portion of the entity of interest while a second portion of the entity of interest is not visible in the inline view, the method further comprising: navigating to from the first portion of the entity of interest to the second portion of the entity of interest from within the inline view; and displaying the second portion in the inline view. 14. The method of claim 12 further comprising: navigating to a third portion of the document from within the inline view, the third portion comprising at least a portion of the document that is not part of the entity of interest; and displaying the third portion of the document in the inline view. 15. The method of claim 14 further comprising: displaying the entity of interest in the document in a manner different from a portion of the document that is not part of the entity of interest. 16. The method of claim 14 wherein navigating to the third portion of the document further comprises: encountering a Frixel effect when navigating across a boundary separating the entity of interest from the third portion. 17. The method of claim 11 further comprising: editing the at least a portion of the document from within the inline view. 18. A computer executable method, comprising: displaying a portion of a code on a user interface; indicating that at least one element in the code has a set of relationships associated with the at least one element in at least one document separate from the code; displaying the set of relationships for the at least one element indicated on the user interface; obtaining the at least one document; inserting a viewport in the code such that the viewport is positioned in a location corresponding to the at least one element; and displaying at least a portion of the at least one document and a history indicator to indicate at least one entity previously displayed in the viewport, the history indicator including a reference to a launch point in at least one of the code or the document and a landing point in at least one of the code or the document. 19. The method of claim 18 wherein inserting a viewport further comprises: creating a visual break point in the code at the location corresponding to the at least one element; and moving lines of code below the location such that the viewport is displayed below the location and above the moved lines of code. 20. The method of claim 18 further comprising: determining an entity of interest in the document, the entity of interest comprising a portion of the document; displaying the entity of interest in the viewport; and causing the entity of interest to be displayed differently from a remainder of the document wherein when a user navigates through the document in the viewport a distinction between the entity of interest and the remainder of the document is illustrated.
Intelligent editors · CPC title
Graphical or visual programming · CPC title
Interaction with scrollbars · CPC title
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 title
Selection of displayed objects or displayed text elements (G06F3/0482 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.