Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API: view management API for non-TextEditors #14483

Closed
siegebell opened this issue Oct 25, 2016 · 6 comments
Closed

API: view management API for non-TextEditors #14483

siegebell opened this issue Oct 25, 2016 · 6 comments
Assignees
Labels
api *duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Milestone

Comments

@siegebell
Copy link

siegebell commented Oct 25, 2016

Request: API support for managing non-TextEditor views. The functionality should support:

In particular, previewHtml should return an object that provides the above functionality,

Example use case: I create a preview for each open document of a certain file type. (The preview is derived from the current state of processing the document; not its contents.) Typically, the documents are all on the left column and their previews are on the right. When interacting with the document, its associated preview should become visible (without receiving focus); moving to a different column than the document itself if necessary. Without this kind of functionality, it easy for the user of my extension to become lost and confused when interacting with multiple documents.

@weinand weinand added the feature-request Request for new features or functionality label Oct 25, 2016
@bpasero bpasero added the api label Oct 26, 2016
@bpasero bpasero removed their assignment Oct 26, 2016
@bpasero bpasero changed the title feature request: view management API for non-TextEditors API: view management API for non-TextEditors Oct 26, 2016
@bpasero
Copy link
Member

bpasero commented Oct 26, 2016

@jrieken fyi

@jrieken
Copy link
Member

jrieken commented Oct 26, 2016

We have a dup for that but I am not finding it right now

@siegebell
Copy link
Author

@jrieken I've seen a couple related issues, but none that request a comprehensive API for managing views.

I'll also amend this request to include views of any TextDocumentContentProvider. (Related: #10379)

@mjbvz mjbvz added this to the Backlog milestone Mar 24, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Mar 24, 2017

I have a few markdown extension feature requests / bugs that all depend on this functionality, namely #8581

@StephenWeatherford
Copy link

We've got data associated with each opened HTML view, which could be very large. So we'd like to know when the tab is closed (not just deactivated) so we can dispose of it.

@jrieken
Copy link
Member

jrieken commented Nov 16, 2017

closing as dupe of #15178

@jrieken jrieken closed this as completed Nov 16, 2017
@jrieken jrieken added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 16, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 31, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api *duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

6 participants