Custom editor support

[thegecko]

What it does

This PR adds initial support for opening the memory inspector using VS Code's build in memory button. It follows the pattern used by the existing hexedit extension.

How to test

Opening the inspector in this way will be possible when this issue is resolved in the VSCode repository: microsoft/vscode#155597

This will require a change in VS Code to allow a user to specify the settings for the memory viewer to use, however I'd like to use this extension as an example when I open that PR.

To test this at the moment, you need to build a custom VS Code, manually changing the extension ID and editor ID found here: https://github.com/microsoft/vscode/blob/e933c1d7b293f77565763d4a85154e1cb1b4cf45/src/vs/workbench/contrib/debug/browser/variablesView.ts#L527

to be:

const HEX_EDITOR_EXTENSION_ID = 'clipse-cdt.memory-inspector';
const HEX_EDITOR_EDITOR_ID = 'memory-inspector.inspect';

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[colin-grant-work]

@thegecko, just changed the wording of your description a bit so GitHub didn't think that this issue would fix the VSCode issue. :-)

[colin-grant-work]

@thegecko, do want to merge this for easier distribution, or just have it available in PR form as an example for reference?

[thegecko]

@thegecko, do want to merge this for easier distribution, or just have it available in PR form as an example for reference?

I'm keen it gets merged and released with our first release. It creates a good test example for the VS Code changes

[colin-grant-work]

I'm keen it gets merged and released with our first release. It creates a good test example for the VS Code changes.

Alright, I'll build a VSCode variant and give it a good test today.

[colin-grant-work]

General functionality looks good. Even plays nicely with the preferences @kenneth-marut-work implemented. Just a minor issue with the URI encoding, but in my testing, using decodeUriComponent did indeed fix that.