-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Fully implement Spyder's new dark theme #8068
Comments
@dalthviz, please continue with the Help plugin. For that I think you need three things:
|
@dalthviz, please continue with
and
Those are very similar. |
And this one too
All of this in the same PR. |
@ccordoba12 @dalthviz I just noticed it now, but the DataFrameEditor's Index column is also not dark themed (making the index invisible), in case that should go into the current batch of work. |
@ccordoba12 @CAM-Gerlach another thing to fix is the setting of the style sheet to detached windows of the plugins: For example with the Editor: |
@dpizetta, keep up the good work!! Things are looking really nice with QDarkStyle 2.6.1: |
It looks pretty neat! Good job for all of you too! I like minimalist icons :) May I change more thing this week, it will even better :) The rounded corners are trick, hauha...there are many things that look weird mixed with flat ones. In version 3 we will have some options to set it flat, rounded and palette changes. I'm looking for the best implementation. Thanks :) |
Thanks so much @dpizetta ! |
@CAM-Gerlach, you know style things is something we can't solve here, so please report them directly in the QDarkStyle repo. It's really a waste of yours and our time (like the issues you open about the icons size, greedy completion text, etc). |
... I responded to you in private chat. |
@ccordoba12 @dpizetta Probably the biggest remaining issue (that has a major UX impact to the point of severly harming usability of specific Spyder features) is that its almost impossible to tell if toggle buttons (like regex mode and case-sensitive for the Find and Replace widget and the Find in Files pane, etc) are enabled or disabled, and they appear to be reversed from what a user might expect. Example: Disabled: Enabled: Therefore, it would seem prudent to e.g. outline them in a much thicker, brighter white or blue when enabled, or even color the icon blue to indicate the button is toggled on. Is this something that can be fixed on Spyder's side, or need it be done in the theme itself? Thanks! |
Hi @CAM-Gerlach those buttons are like in the toolbar, they are transparent, but when activated they change to the background color, which is your color there. Both colors are the same in this case. I think when the pressing event is occurring they appear blue in the border. I've tried to put some color (lighter) when not activate and the other (darker) when activated, but they made the interface ugly. There are some changes that can be made to improve (Qdarksytle and/or Spyder):
In normal style, they are identical to the push buttons. Ideas? @ccordoba12 @goanpeca @CAM-Gerlach Tks |
@bcolsen I can confirm that's what I see on Windows as well. (Qt 5.9.7). |
I back @CAM-Gerlach concern regarding the toolbar buttons. I think they need to change in a more visible/obious way than just the outline. I find it not clear enough (even if some other tools like VSCode do this) (I don't think this is clear enough, I want to know I can click on something without having to move the mouse pointer there) @dpizetta I believe we should start using the power of SASS to add lighter and darker shades besides the basic 9 color palette to address these small tweaks. |
I agree, although even VSCode's look would be clearer than what we have right now, which is virtually impossible to tell and looks "backwards". Ideally, though, we want the whole button to be a different, ideally darker color to make clear its depressed (which could require lightning the toolbars). |
2.6.7 is the latest on |
You mean add that in conda forge :-p ? |
@goanpeca No, its already on 2.6.8 there. |
Done. |
Another issue I've noticed for a while: The right sidebar that shows error/warning/etc. markers throughout the document is not offset to match the scrollbar, so the latter is not usable as an indicator of which should be visible. Compare the light theme: With the dark theme: Presumably, the warning bar needs to be offset by a distance equal to the scroll arrow widget on the top and bottom on the dark theme to avoid this problem. @dpizetta @ccordoba12 @goanpeca Ideas/opinions on how to handle the toggle icons being impossible to tell if activated? This is probably the most important item on this list to fix, since it has major usability impacts for Find/Replace and Find in FIles. |
This has nothing to do with the dark theme. Please open a new issue about it. |
@ccordoba12 I opened a new issue, but I am rather confused. Could you explain how a UI problem that occurs only under the dark UI theme has |
Because it happens when the editor background is dark, irregardless of the theme, as your screenshot above shows. |
Ups, sorry, I didn't read your comment completely. I thought both themes have the problem. In any case. we'll close this bug after we fix the foreground color of Sympy output, so it's better to open new issues. |
No problem, we all miss things. I just wasn't sure if it was me this time.
Okay, I'd been avoiding that before since you'd told me not to do so. So should also I open new issues for
and, if its determined that the best course of action is to fix it in Spyder, since @dpizetta said it could be solved in either as I understand,
? |
I already edited the description to cover those cases, Please see above. |
@ccordoba12 Okay, thanks. I couldn't see that it had been updated while I was editing it myself to similar effect, heh. I already had posted a screenshot here, so I'll just copy that to a new issue. @dpizetta Do you want me to open an issue over on QDarkStyle for the toggle icons issue with the content from over here, or are you already handling that? Thanks! |
Please, @CAM-Gerlach, I'm already working on this. The reasonable option, for now, keeping the border highlighted when checked like the lastest version of vscode. We (@goanpeca) can try other options with scss in the future. |
@dpizetta Thanks. Per your direct request, I opened an issue there. |
Since the fix for the dark theme will be out with version 4, I thought of a workaround for the current version. The only problem now seems to be the colour of the icons in the window. After going through the source files, I found that the icons for the spyder3 theme are configured in directory_of_spyder/spyder/utils/icon_manager.py. (The directory of spyder is /lib/python3.7/site-packages/ if installed through pip). I changed the variable _qtaargs by adding the parameter colour white wherever necessary. The final result is as shown in the picture below. The dark mode works perfectly everywhere except some parts of help and Qt documentation. I have attached the modified icon_manager.py file. Cheers! |
No workarounds will be added for the current version, sorry. |
With the exception of issue #9545, we can say this is finished. Thanks to everyone who contributed to making the dark theme for Spyder a reality! |
By the way, if you find more problems about the dark theme, please report them as separate issues. |
Problem Description
This issue serves to track the sub-issues related to fully implementing the dark theme across Spyder's various panes, text and icons, as a number of steps, both internal to Spyder's codebase and external in
QDarkStyle
, are required.Blocked by #8020 , the initial implementation. Originally spawned from #2350 , the initial issue and discussion thread.
Places that need to be "darkified":
Output
windowNon-inline plot dialog (not sure if possible)@ccordoba12: This is not possible because that dialog is created by Matplotlib."Information" icon in file switcher isn't themed(opened as a separate issue to close this one out)Places that still have black/dark colors:
names
columnCommand to Execute
columnOther Spyder Issues/Bugs:
Right code analysis sidebar does not match scroll bar position(will be deal with separately)External Issues:
The text was updated successfully, but these errors were encountered: