-
Notifications
You must be signed in to change notification settings - Fork 283
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
feat(ux/#2496): Configurable statusbar #3402
base: master
Are you sure you want to change the base?
Changes from 10 commits
cd08482
21a2c5d
775b3e8
91793e1
42dd87d
cb9822c
745c3f8
b3e5bac
203c4ec
600c48a
402e3cf
6792f0b
c552736
34bd310
9744bff
c3475c1
2bde61c
de6585b
5b75ef2
b43dcce
df930d9
aa2b3ee
efcd50b
c69fb1e
f10f07b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -36,6 +36,12 @@ let getDefaultConfigString = configName => | |
"workbench.sideBar.location": "left", | ||
"workbench.sideBar.visible": true, | ||
"workbench.statusBar.visible": true, | ||
"workbench.statusBar.items": { | ||
"left": ["notificationCount", "macro", "leftItems", "diagnosticCount", "git"], | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It looks like we'll need to replace There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (Oops, this was just echoing what @z0al mentioned in his reply - beat me to it!) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Instead of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I noticed in the demo from @bryphe below that we need to adjust the default configuration shipped in Oni to eliminate the spacing gap between notification items by default. It's caused by items hidden due to To remove the spacing we can adjust the default configuration to something like this. {
"workbench.statusBar.items": {
"left": ["notificationCount", "diagnosticCount", "notification", "..."],
"right": ["...", "modeIndicator"],
"showOnNotification": ["notificationCount", "modeIndiactor", "diagnosticCount"]
}
} There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually that's not necessary, but it might be a good idea, to make By default, Also, I changed the code now so that the "start": ["aa", "bb", "cc"]
"showOnNotification": ["aa", "cc"] Then it's shown as ["aa", "cc", "bb"] And then I added a new There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure I follow. I thought But the point I was trying to make is to explicitly define the
That can also be a fix for the issue. But the reason I didn't suggest that because it rearranges some of the elements on the status bar only to revert back to the original positioning a second later, I think that can result in a bad UX. But I didn't see it in practice, maybe it's not that bad. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Sorry I have seamed to not explain my self correctly... It will be shown as this all the time not only for the notification ["aa", "cc", "bb"] There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh, I see, I misunderstood. If I get it correctly now, it means we will automatically group notification items even though the user might have chosen a different positioning. To force the items to be kept in the same position as the configs the I feel like that defeats the purpose of explicitly positioning the items via configs... in general, I'd try to make things Simple and Stupid. In this case, It seems like we are adding complexity for a little gain especially since the fix for gapping can be done by the user him/herself with little effort. We just need to make our defaults gapless. But I also feel like I'm being too picky here, sorry. so I'd leave it for @bryphe to decide what makes sense. Thanks for the great work on this 🙇🏻♂️ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. | Oh, I see, I misunderstood. If I get it correctly now, it means we will automatically group notification items even though the user might have chosen a different positioning. To force the items to be kept in the same position as the configs the keepPosition mode must be set, right? Yes
True, true then maybe what we have to do it's have default to match what the user put and then maybe have a |
||
"showOnNotification": ["modeIndicator", "notificationCount"], | ||
"rigth": ["rightItems", "lineEndings", "indentation", "fileType", "position", "modeIndicator"], | ||
"hidden": [], | ||
}, | ||
"workbench.tree.indent": 2, | ||
"vim.useSystemClipboard": ["yank"] | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be great to document the 'notificationMode' and 'hidden' properties here, too!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! 👍
Although I would ask for anyone to check the docs that I made, because I am not good with words...