Skip to content
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

Treeview/Sidepanel layouting #1760

Open
DiegoJArg opened this issue Apr 3, 2024 · 6 comments
Open

Treeview/Sidepanel layouting #1760

DiegoJArg opened this issue Apr 3, 2024 · 6 comments
Labels

Comments

@DiegoJArg
Copy link

Not an issue, but I would like you to review these ideas about layout for future versions if possible. :)

  • Name of the first/main folder steels pixels from the TreeView not adding any value, pushing/indenting following items to the right. It may provide some value if that folder-name gets drawn as title of a tab.

  • Blank space below the treeview is not usable. It may be reduced if the treeview could be moved as a tab to another split-view.

image

@Guldoman Guldoman added the UI/UX label Apr 3, 2024
@Guldoman
Copy link
Member

Guldoman commented Apr 3, 2024

Name of the first/main folder steels pixels from the TreeView not adding any value, pushing/indenting following items to the right. It may provide some value if that folder-name gets drawn as title of a tab.

Yeah this is an interesting proposal. The main issue is that we support multiple projects at once, so only the first one would have the name in the tab.
I guess we could consider if for when we only have one, and revert to a TreeView item when more are present.

In general I think we could reduce the indent size in any case, as it's a bit too much. Same for the padding around the chevron.

Blank space below the treeview is not usable. It may be reduced if the treeview could be moved as a tab to another split-view.

How would you deal with this?
I don't think we have anything that could go under the TreeView at the moment.
Maybe some plugin could add some content there, like a list of commits.

@DiegoJArg
Copy link
Author

If this side panel could be a tab. I would move it to the lower-right corner, sharing the place with my TODO list.

I don't usually like side panels on the left, because resizing them moves the main view of the code, not only distracting my eyes, but also forcing to redraw that view just to see more in the panel. But this is a lightweight editor that doesn't seem to have any trouble with redrawing. I love it.

@Guldoman
Copy link
Member

Guldoman commented Apr 3, 2024

If this side panel could be a tab. I would move it to the lower-right corner, sharing the place with my TODO list.

We have plans to allow positioning it into (left and right) side-pockets that allow tabbing and vertical splitting, so I guess this would work out for you.

But this is a lightweight editor that doesn't seem to have any trouble with redrawing. I love it.

Glad to read that!

@DiegoJArg
Copy link
Author

Understood! That would certainly help.
But wouldn't converting it to a Tab solve that need more easily ?
It may do use of a space of the screen which is today already totally adjustable by the user.
I guess the difference would be that a side panel has the option to be hidden.

@RednibCoding
Copy link

RednibCoding commented Apr 4, 2024

What about organizing projects with accordion ui elements as shown in the screenshot?

image

@DiegoJArg
Copy link
Author

It is much thinner. That is good.

My opinion towards most side panels is that normally are dead-screen-space at a 99% of the time.
But a minimalistic file navigation adds value by being a short-cut to quickly open currently-closed-files within the project or its context. For everything else, the correct tool should be a normal file explorer.

I would suggest a "speed-dial-tab" such as some browsers have after opening a "new tab".
In that way, its content will only be shown when it is relevant and, strengthening the current tab-based navigation and multi split capabilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants