-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[theia] Need a clear distinction between the navigator and the editor #1057
Comments
Just so you are aware, the fact that the separator line is not always shown is because you are not running on the default zoom-level. |
We are going to make layouts quite flexible, so that you can move any widget anywhere. Different backgrounds will therefore not work. |
@lmcbout you can use Ctrl-0 to get to the default zoom level (that's Ctrl-zero) |
A different tone of "gray" or the editor color would help also, I think it's like that in Atom and vscode afaik. |
Besides that it doesn't look good (IMHO), it won't solve the issue as it only increases contrast between editors and non-editors (see #1057 (comment)) |
#2 and #3 increases the contrast which makes it easier to see the limits of the editor and the panel on the side. However it greatly decreases editor usability in itself with the contrast being wrong with the text. I agree with above and think we should wait until flexible layout is in and see if we can improve something then. |
there is a distinction between editors/widgets with the added border |
We need a clear distinction between the navigator and the editor. Both use the same background colour. If you look at the sidebar menu, the background is another colour and the user can see a proper distinction between the side menu-bar and the navigator or

editor. The distinction is not there between the navigator and the editor
The text was updated successfully, but these errors were encountered: