Commit graph

20 commits

Author SHA1 Message Date
João Moreno
ec805db5ed
add repository field to extensions package.json 2021-01-29 15:30:45 +01:00
Matt Bierner
ea13176ee9 Enable image preview for avif images
Fixes #106415

Support for these was added in electron 11
2021-01-13 13:52:34 -08:00
Alex Dima
2fa41fb23e
Add "web" as extensionKind to extensions which support this 2020-07-24 10:41:03 +02:00
Martin Aeschlimann
16be2c9885 used shared webpack-config for browser 2020-06-25 23:22:02 +02:00
Matt Bierner
0145e38e5f Enable the image preview in web/serverless
Fixes #99802
2020-06-10 16:44:10 -07:00
Matt Bierner
dc68e6578e rename custom editor activation event
For #77131

Renames the activation event from `onWebviewEditor` to `onCustomEditor` to be consistent with the reset of the API
2020-02-26 10:59:36 -08:00
Matt Bierner
dc1e7871b8 Rename custom editor contribution point
Renaming to match new API proposal
2020-02-25 10:55:41 -08:00
Matt Bierner
b0fb9f17da Note image preview's extension kind
For #85819
2019-12-02 15:43:37 -08:00
Matt Bierner
f085deb2e0 Remove test editing code from preview 2019-11-22 15:18:01 -08:00
Matt Bierner
d9c4923f98 Fix trailiing comma 2019-11-20 21:36:05 -08:00
Matt Bierner
8fa16bd74f Remove custom editor support for data uris
For #85203. Data uris are no longer used by VS Code core
2019-11-20 21:35:29 -08:00
Matt Bierner
60f8583d95 Adding setting to enable a test command for making a fake "edit" to an image preview
This will be use for testing custom editors
2019-11-12 16:08:04 -08:00
Matt Bierner
f50c8264fa Don't try rendering TGAs in the built-in image preview
Fixes #84533

Looks like tga is not currently supported by Chrome
2019-11-12 14:36:22 -08:00
Matt Bierner
6803eba9fe Add zoomIn and zoomOut commands for image preview
Fixes #71653

Adds two new commands, `imagePreview.zoomIn` and `imagePreview.zoomOut`. These zoom the active image preview in or out. They have no default keybinding but users can configure one for them
2019-10-22 17:11:31 -07:00
Matt Bierner
f462eab969 Adding builtin priority for custom editors 2019-10-15 16:45:15 -07:00
Matt Bierner
aeae28bf2c Remove tiff as a supported image preview format
Fixes #81803

This is not supported by chromium
2019-10-01 15:41:56 -07:00
Matt Bierner
6b947b14ed Fix image preview extension for remote
Fixes #81434

- Make image preview a ui exension

- Add logic so that `asWebviewUri` supports preserving the scheme of the requested resource. This is important as we know where to load the resource from
2019-09-25 16:25:40 -07:00
Matt Bierner
d54dbd33f4 Add icon for image preview ext
Fixes #80677
2019-09-16 16:02:56 -07:00
Matt Bierner
04da82c1d2 Let webview editors show in diff original view too
Fixes #80740

The original view in diff views uses a data uri instead of a resource on disk. Make sure our webview editors can register themselves to handle this case too
2019-09-16 14:17:34 -07:00
Matt Bierner
011836a150
Prototyping custom editors (#77789)
* Custom Editor exploration

For #77131

Adds a prototype of custom editors contributed by extensions. This change does the following:

- Introduces a new contribution point for the declarative parts of a custom editor
- Adds API for registering a webview editor provider. This lets VS Code decided when to create a webview editor
- Adds an `openWith` command that lets you select which editor to use to open a resource from the file explorer
- Adds a setting that lets you say that you always want to use a custom editor for a given file extension
- Hooks up auto opening of a custom editor when opening a file from quick open or explorer
- Adds a new extension that contributes a custom image preview for png and jpg files

Still needs a lot of UX work and testing. We are also going to explore a more generic "open handler" based approach for supporting custom editors

Revert

* Re-use existing custom editor if one is already open

* Don't re-create custom editor webview when clicking on already visible custom editor

* Move customEditorInput to own file

* First draft of serializing custom editor inputs

* Use glob patterns instead of simple file extensions for matching custom resoruces for custom editors

* Add descriptions

* Try opening standard editor while prompting for custom editor

* Make sure we hide image status on dispose

* Make sure we restore editor group too

* Use glob patterns for workbench.editor.custom

* Allow users to configure custom editors for additional file types

* Use filename glob instead of glob on full resource path

* Adding placeholder for prompt open with

* Add enableByDefault setting for editor contributions

* Enable custom editors by default and add `discretion` enum

Changes `enableByDefault` boolean to a `discretion` enum. This should give more flexibility if we want other options (such as forcing a given custom editor to always be used even if there are other default ones)

* Allow custom editors to specify both a scheme and filenamePattern they are active for

* Rework custom editor setting

* Don't allow custom editors to be enabled for all resources by a config mistake

* Replace built-in image editor with one from extension

* Adding reopen with command

* Improve comment

* Remove commented code

* Localize package.json and remove image

* Remove extra lib setting from tsconfig
2019-09-10 17:56:57 -07:00