-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate to rewrite workbench layout using grid widget #50853
Comments
Some prerequisites for the grid widget before this can happen:
|
Splitview now supports:
🎆 Another related commit: c01cf1d |
Gridview now supports all of that too! 🎉 Getting closer |
Awesome 👍 |
This looks really cool, if it's what I think it is. One thing I'd be curious to know - would this include the possibility of having multiple terminal splits/sections as part of the grid? That would enable some great workflows available when working in a terminal environment, but with the extra Visual Studio Code polish and better debugging experience. Or does this include putting the whole panel in a split? Which definitely represents progress but doesn't get Visual Studio Code all the way to what I'm proposing 😃 |
@joaomoreno oooo will try this today |
Didn't actually run it, so might not be complete, but you get the idea. |
Moving to Feb. |
Please note that ideal decoupling should not be just about choosing left/right position of the whole sidebar, but the ability of position each element in whatever panel the user wants, i.e. treeview at left, open files at right, and search at bottom... all at the same time! |
closing this item as I believe we have tackled "investigation" :P |
Given the introduction of the grid widget, we should explore to use it as the driver for the workbench layout, at least for the parts that are connected via sashes:
Related issues:
Grid widget prerequisites
The text was updated successfully, but these errors were encountered: