Add drag and drop for contributed tree views

[Krzysztof-Cieslak]

We've been using new Tree View API to provide structured view of F# projects - in F# project files needs to be ordered according to compilation order so this additional view gives users better information about their project. We also include in the view list of project references, and assembly references so it's really similar to the Visual Studio solution explorer.

It looks like following:

As I've mentioned - ordering of files is really important for the F# projects, and we provide couple of helper commands to manage it (move file up/down etc). Those commands work more or less, but I don't think it's best UX.
I think it would be super nice if users had ability to use normal drag and drop to manipulate the order - just as they are able to manipulate files in normal file explorer (drag and drop files to move them to subfolder for example)

[cartermp]

Just to add weight to this: file ordering is critically important for F# users. We're also exploring adding click and drag for CPS in Visual Studio, which would leave VSCode as the only F# editor that doesn't support click and drag for file ordering.

[forki]

Oh that would be an awesome feature!

[mastoj]

💯 * 👍

[hakonrossebo]

+1

[DmitryBatalov]

+1

[priort]

That would be a really helpful feature.

[priort]

+1

[magnushammar]

This would be awesome. Some things are actually better done with a GUI and this is one.

[pirrmann]

+1

[Neftedollar]

F# developers need this feature as an air.

[MangelMaxime]

💯

[schaveyt]

+1

[DanTup]

I'd like to see this too for a UI tree we're building. Some things it'd be nice for the API to support:

• Declaring if a node is draggable or not
• Ability to drop on top of or in between items (re-order versus changing parent)
• Ability to provide feedback while dragging about whether a given location is valid to drop on

[FrederickBrier]

Someone wrote that we need to wait for the vscode team to implement the feature. Does that mean that we should not fork the repo and try to implement it? Because that that is not their process and a pull request would be rejected? Thank you.

[zhaoyi0113]

any update about this requirement?

[sandy081]

No plans yet.

[nickzhums]

To provide some additional info from VS Code Java team. We've been hearing feedback that developers want this kind of drag and drop feedback from our past survey and customer development.

In addition, some of the community videos have mentioned about this feature request as well (https://www.youtube.com/watch?v=uq4GjRF_860&ab_channel=JavaBrains) - 33:20 (Video itself has 78K views)

Would be great if we can support drag and drop in tree view soon and make this higher priority - thanks!

[nickzhums]

Hello folks, just wondering what the current plan for this feature is ? We have customer feedback that they find this missing in the Java Project Explorer and think it is inconvenient - thanks!

[gplumb]

Hi all! Would be good to know if this made the cut from last year's roadmap or not :-)

…

On Fri, 14 Jan 2022 at 06:45, nickzhums ***@***.***> wrote: Hello folks, just wondering what the current plan for this feature is ? thanks! — Reply to this email directly, view it on GitHub <#32592 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFU7ZU6X6UGDM4QH7EQPXDUV7BAXANCNFSM4DXAOV5A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[gjsjohnmurray]

Would be good to know if this made the cut from last year's roadmap or not :-)

It was on the current iteration plan (#139607) until 10 days ago, then removed by @kieferrm (not moved into the Deferred section though). But there's evidence of work on it by @alexr00 recently, so I think it stands a chance of landing in 2022.

[alexr00]

@gjsjohnmurray is correct, it does stand a chance of landing in 2022. We're just going through our API process and refining it now.

Folks who are interested in it can try out the current API proposal and provide feedback in this issue if you want to help!