Allow changing the selection using the TreeDataProvider

[orta]

• VSCode Version: 0.13.0
• OS Version: macOS 10.12.x

Steps to Reproduce:

1. Write an extension that uses the TreeDataProvider API to show a UI
2. Desire to be able to set the selected state programatically

I built an extension ( more details are in #28325 ) and in doing so, I really started wanted to be able to set the selection state programatically.

[mike-lischke]

Any chance we get this in a soonish timeframe? The custom view (TreeDataProvider) interface exists now for while but is still very limited (no formatting, no tooltips, no per-node icons, no programmatic interaction like this selection change, expand state, no checkboxes, no columns etc.).

Extension writers could do a lot of cool things if we would be given the necessary APIs. Since these views are a major navigation element in vscode, I think they should get much more love from the vscode devs.

[sandy081]

@mike-lischke

TreeDataProvider api supports icons for nodes. May I know what do you mean by per-node icons?

Also Can you please elaborate about fomatting request?

[mike-lischke]

Well, it's pretty easy. A good start would be to give us all the possibilities the file tree has got:

1. It has icons per file type (hence per-tree-node-icons). We want that too.
2. It has colors for text, also a want-to-have. Markup support, like we have for tooltips in the code editor, would be awesome.
3. We need to show additional informations per node with a tooltip (at least long text should be shown there).
4. We must be able to select nodes (yes: multi selection) per code and read out the current status.
5. Check box support is also a pretty common requirement.
6. Multi column support is something I need as well. This content:

would then show much nicer. All the individual values nicely aligned.

7. Finally, the views should support docking, so that they can be spread accross all the available space. Currently I have 10 views stacked vertically. Even on a 4K screen this is all but easy to consume.

However, this list goes much further than the simple selection request. If you want I can open a new Github issue.

[mike-lischke]

I guess my list should go to #27823. Then we could close this issue here.