Skip to content

Alternative locations for the outline view #49923

Closed

Description

The outline view lives inside the file explorer and while it can be re-arranges in there it cannot be dragged into its own view. Alternative locations could be:

  1. a standalone viewlet,
  2. inside another viewlets,
  3. the bottom panel, or
  4. as a re-arrangable view that can be docked anywhere in the UI (like most others have it).

Activity

  1. DanTup commented on May 16, 2018

    @DanTup
    Contributor

    I have an ultrawide monitor and would prefer to dock this on the right side (separate from the existing sidebars). However, I can also imagine that on smaller screens (like a laptop) people would prefer it in the existing sidebar (some might want it in explorer, some might want it on its own tab).

    Honestly, I think the best thing would be for all sidebar buttons to be individually dockable (eg. so I could have files and debug views visible on opposite sides of the window, or even docked into the same left sidebar). I think it'd be better to do something that works with the existing views than something specific for Outline.

  2. gulshan commented on May 16, 2018

    @gulshan

    I think, outline should be a viewlet. But viewlets should become more flexible in general, at least ability to dock any of them left or right, independent of other viewlets, is desirable .

  3. Ettemlevest commented on May 16, 2018

    @Ettemlevest

    Danny Tuppeny (@DanTup) & Gulshan (@gulshan) That's a good idea. I would love to use outline viewlet permanently docked to one side and use every other viewlets in the other side.

  4. Krzysztof-Cieslak commented on May 16, 2018

    @Krzysztof-Cieslak
    Contributor

    I think, outline should be a viewlet. But viewlets should become more flexible in general, at least ability to dock any of them left or right, independent of other viewlets, is desirable .

    💯, it would solve the problem of increasing amount of viewlets contributed by extensions and constant switching between them

  5. ToMakeSense commented on May 22, 2018

    @ToMakeSense

    visual studio, Eclipse, webstom etc... I think it's obvious

  6. jrieken commented on Jun 8, 2018

    @jrieken
    ContributorAuthor

    adding Isidor Nikolic (@isidorn) since this is about the workbench layout

  7. gulshan commented on Jun 8, 2018

    @gulshan

    Linking showing two sidebars issue- #26777

  8. regs01 commented on Jun 10, 2018

    @regs01

    Gulshan (@gulshan) i like the new way of Code Outline extension, but still it should be optional. Not everyone would like it in an own viewlet.

  9. ghiscoding commented on Jun 11, 2018

    @ghiscoding

    Johannes Rieken (@jrieken)
    Wasn't there a breadcrumb option as well? I would prefer that alternative, I always like having it on top right corner, the same default as VS. As long as I can have it on front stage at all time without having the solution explorer always open.

  10. jrieken commented on Jun 11, 2018

    @jrieken
    ContributorAuthor

    Ghislain B. (@ghiscoding) Yeah, breadcrumb is an option that we explore this milestone, see #9418

  11. 156 remaining items

  12. Serhioromano commented on Mar 5, 2021

    @Serhioromano

    We reallllllllllllly need this feature. please

    The most annoying thing here that as a programmer myself, I'm pretty sure it is rather easy to implement a new 3rd optional panel which has the same functionality as the console docked to the right.

    If you think it is an easy task, just do it and submit PR. I am also programmer myself and I see it as one of the most complex task for VS Code.

  13. RollingHog commented on Mar 5, 2021

    @RollingHog

    The most annoying thing here that as a programmer myself, I'm pretty sure it is rather easy to implement a new 3rd optional panel which has the same functionality as the console docked to the right.

    If you think it is an easy task, just do it and submit PR. I am also programmer myself and I see it as one of the most complex task for VS Code.

    Uh, an angry russian programmer here. Sir, I am not a contributor of VS Code and it will take literally days of grep-ing to understand structure and "default ways" of such complex project. At the same time, adding a new (optional and hidden by default) entity similar to already existent "Ctrl+J Panel" should not be difficult if you already know the code; it is something like three positions in the "Appearance" menu (show and move Panel2) and some tinkering to avoid collisions with already existent Panel. Where am I wrong?

  14. jrial commented on Mar 5, 2021

    @jrial

    Where am I wrong?

    In treating this like a discussion area, a soapbox, a pub, ... It's not. It's an issue tracker.

    You said you're a programmer, so I'm sure I don't need to lecture you on its correct use.

  15. rafaelsierra commented on Mar 5, 2021

    @rafaelsierra

    Guys, please if you don't have anything to add that will move this issue forward, please refrain from commenting.

    There are people following this issue (like me) waiting for news but just getting spammed by "this should be easy", "it has been 3 years, where's my panel!?" and such.

    Again: if you do not have a PR or new information that will help this to be accomplished, please refrain from commenting.

  16. AmbrosiaDevelopments commented on Jul 24, 2021

    @AmbrosiaDevelopments

    Not sure if mentioned already, can't be bothered to look through the spam. However, moving outline to the same panel as terminal then moving that whole panel to the right gets you half way there. With the most recent update you can now open terminals inside the editor area. You just drag this new editor pane to the bottom where the old terminal panel used to be and you're done.

    image

  17. byehack commented on Aug 4, 2021

    @byehack

    @SimonDever
    it's not good idea when working with splited editor groups. (try to add terminal at bottom after split the editor)
    <btw we should have three panel (left/right/bottom) at same time.>

    image

    maybe we should request new feature to improve better grouping?

  18. Lorenz-N commented on Aug 28, 2021

    @Lorenz-N

    Besides what's already been told, from the extension developer perspective, it would be also great to allow re-using the Outline view in custom Side Bars. I'm aware of the options we have to create our own Outline via TreeViews but it would be another step backwards to something the previous code outline extensions already provided just to have it in another view... doesn't sound effective at all to me.

    Plus, there is some extra stuff happening on the built-in Outline view (watched the source before and compared to TreeView alternatives), which is great, but it would make more sense to re-use that functionality across extensions and focus on extending the built-in views instead of having it hardcoded to the Explorer... sadly trying to use the id on custom views leads to:
    ... A view with id 'outline' is already registered..

    Would also add to allow the same customization as with TreeViews or providing an API that covers both (I assume it's actually just a TreeView in the end) ... but that's probably another topic.

  19. gjsjohnmurray commented on Oct 25, 2021

    @gjsjohnmurray
    Contributor

    The new side panel (an experimental feature in 1.61) should resolve this. See #132893

  20. silentred commented on Oct 25, 2021

    @silentred

    The new side panel (an experimental feature in 1.61) should resolve this. See #132893

    Thanks. I think this issue is well resolved. Just add "workbench.experimental.sidePanel.enabled": true to user setting and restart VSCode. Enable "View"-> "Appearance" -> "Show Side Panel".

  21. gustavz commented on Nov 16, 2021

    @gustavz

    puh that was hell of a ride :D thanks for this feature, finally!

  22. manojbaishya commented on Nov 16, 2021

    @manojbaishya

    The new panel does not get hidden in Zen Mode.

  23. KamasamaK commented on Nov 16, 2021

    @KamasamaK

    The new panel does not get hidden in Zen Mode.

    You should put any feedback you have specific to the new panel in its own issue at #132893.

  24. jrieken commented on Dec 21, 2021

    @jrieken
    ContributorAuthor

    Closing. All thanks to SteVen Batten (@sbatten) 🍻

  25. locked and limited conversation to collaborators on Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

feature-requestRequest for new features or functionalitylayoutGeneral VS Code workbench layout issuesoutlineSource outline view issues

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions