Hintbox work in progress

[bfitzpat]

This came out of the idea that was mentioned at the Fuse Sync Call for an easy way to bubble up some of the buried functionality of VS Code such as useful settings (like the Runtime switch @apupier mentioned) or commands.

Definitely a work in progress, but the high-level idea is that we would have a simple webview in the view side that could possibly change based on content of a particular editor that's open. Not much room, so would limit to maybe the top 5 useful tips or settings that would apply to a particular context.

For instance, if I create one of these for editing Didact files (which is likely), it would be a simple list that would appear if you have a Markdown or AsciiDoc file open in an editor:

• Use Ctrl (or Cmd)+Alt+V to preview your file in the Didact preview window

Signed-off-by: Brian Fitzpatrick bfitzpat@redhat.com

[bfitzpat]

This demo just shows how it might appear to the user with a static Didact page and a couple of options, but to push forward I would:

• Refactor the code to avoid so much duplication between DidactPanel and HintBoxViewProvider
• Provide a simple example for Didact file editing (adoc/md) as described in my initial comment
• Explore how best to change the activation events to support files from other extensions (such as Camel K or AtlasMap) so that these bite-sized hint didact tutorials would be easy to produce and package with other projects
• Add better documentation about how to define one of these, with guidelines on avoiding lengthy views (though scrollbars do work)

[bfitzpat]

(Note that the failing windows test should be fixed by the work done in #448 when it gets approved and merged.)

[bfitzpat]

Leaving this open for now to explore other options like the new welcome screen in VS Code that we may be able to leverage.