-
Notifications
You must be signed in to change notification settings - Fork 239
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
new proxmox version update undid dark theme #142
Comments
Hi, I have not upgraded my servers to the new version yet, could you provide a screenshot of what you mean? There will be some time before I can be able to look at what exactly is changed and what I need to add. |
That person probably means this: https://imgur.com/a/SHV81jl |
I see, thanks. There are a bunch of things I would also like to fix. Will attempt to catch up to the latest release soon (probably either this weekend or the next). |
Today I tried some things and found what needs to be done to get grey icons for stopped VMs, lxc, unavailable storage and changes to template icons. EDIT: I changed the grey to be a lttle lighter, this also addresses #140 now. ADD.fa-fw.x-grid-icon-custom.fa.fa-cube.stopped { .x-tree-icon.x-tree-icon-custom.x-tree-icon-leaf.fa.fa-desktop.stopped { .fa-fw.x-grid-icon-custom.fa.fa-desktop.stopped { .fa-fw.x-grid-icon-custom.fa.fa-database.available { .x-tree-icon.x-tree-icon-custom.x-tree-icon-leaf.fa.fa-tags { .fa-fw.x-grid-icon-custom.fa.fa-tags { CHANGE.x-tree-icon.x-tree-icon-custom.x-tree-icon-leaf.fa.fa-cube { .x-tree-icon.x-tree-icon-custom.x-tree-icon-leaf.fa.fa-desktop { .x-tree-icon.x-tree-icon-custom.x-tree-icon-leaf.fa.fa-file-o:after { .fa-fw.x-grid-icon-custom.fa.fa-file-o:after { .fa-fw.x-grid-icon-custom.fa.fa-database { |
Thanks, will get these changes in soon. |
Thanks to you both for working on this. Once I realized I was back in light mode, I figured the last update had killed the theme and decided to remove it to avoid any issues. The uninstall command says there's no theme installed.
Will I need to do anything to clean out the old theme files before re-running the script when the theme is updated? Thanks! |
@johntdavis84 clearing your browsers cache should remove it. |
@johntdavis84 whenever you install an update of the „pve-manager“ package, the theme will be overwritten by the default from proxmox. Then you need to re-install the theme everytime. Edit: I forgot, either a reboot or a restart of pve-proxy might be necessary for theme changes to show up (I wrote a script for all that on my pve) @Weilbyte - perhaps this should be mentioned in the readme or as a wiki entry. |
@djraw only a browser cache clear should be necessary. |
Yes, I forgot my script also updates certificates which makes the restart of pve-proxy necessary. But anyway I'm right about the updates to pve-manager, after that a reinstall of the theme is needed. And that might be added to the readme. |
@wommy @johntdavis84 @djraw reinstalling the theme should fetch these latest changes. Let me know if it works. |
looks great! so glad i complained 🤣 🤣 🤣 didnt know it was all sass, |
I think it looks ok as well but my only concern is how it will look on older versions, which I will attempt to test soon. And yeah, it's all sass; it's still spaghetti but at least more manageable than if it was pure css 😓 |
since css custom properties, its been much more managable i could help with a migration |
Works perfect for me, thanks @Weilbyte :) Edit a few hours later: I just realized that the root "Resource Pool" fa-tags is still darker than the tags below it. @Weilbyte You forgot this addition to get it lighter (as asked for in #140): This time I went ahead and created the PR #146 |
@djraw I will look into it soon. Added a comment on your PR. |
i like their new disabled VM transparency, very clear which are running / not running
The text was updated successfully, but these errors were encountered: