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

script to create inverted colors skins, and a LateDay skin #11638

Closed
wants to merge 0 commits into from

Conversation

michelealbano
Copy link

@michelealbano michelealbano commented Jun 9, 2023

I developed a python script that visits the folders containing a skin, and re-creates in the current folder the same folder structure, copies locally the png / psd files, and for everything else it copies the files but inverts the colors.

This PR could solve issue #9217

@github-actions github-actions bot added the skins label Jun 9, 2023
@ronso0
Copy link
Member

ronso0 commented Jun 9, 2023

Interesting! (I didn't look into the details, yet. )

In general the easiest way to fix #9217 would be another color scheme for an existing skin (for LateNight preferrably). Creating yet another skin increases the maintenance burden, especially if we just duplicate an existing skin.

Could you look into making the script work with the existing LateNight architecture and use the PaleMoon scheme?
Each scheme has a

@michelealbano
Copy link
Author

As suggested, I have no new skin anymore, but a color scheme for LateNight. Solving #9217 possibly

@ronso0
Copy link
Member

ronso0 commented Jun 9, 2023

Thank you, I'll check this out next days.

I think this can go into the 2.4 branch.
Also there are quite a few unrelated changes in skin.xml that indicate you worked off the 2.3 branch (or an older version of the main branch?). Please take a look, rebase if required and force-push so we can change the target branch here.

@michelealbano
Copy link
Author

michelealbano commented Jun 9, 2023 via email

@daschuer
Copy link
Member

daschuer commented Jun 9, 2023

Skin changes can go to 2.4-beta. Release is scheduled at 2023-08-08 so no stress, if you miss that date we will merge it to 2.5 which will be released 6 month later.
Target your work at the 2.4 branch in any case.

Just last weekend it was itching me that the Shade skin is good for sunlight, but the library is not.

I did not had a look to the script, is it similar to the color shema implementation of Shade? In that case, the colors from the PNGs are replaced on the fly. However recalculating the colors from the library css is missing.

Can you script help here?

@ronso0
Copy link
Member

ronso0 commented Jun 12, 2023

@michelealbano When you rebase could you please separate the changes into

  • add script
  • add PaleSun scheme

The color inversion seems to work but the theme itself is not usable IMO

  • most button icons are hard to recognise, the dark outlines that should increase local contrast now make the icons appear muddy
  • text/background contrast is as low (or even lower?) as in PaleMoon, but for daylight we need high contrast
  • knobs are hard to read

image
image

Bottom line: simply inverting the colors doesn't produce a daylight skin. I think the issue is that the script handles all colors the same way (or misses some SVG colors?) and can't really replace manual labor.
I chose distinct colors in most places (e.g. #000001 instead of #000) so they can be bulk-changed with simple find & replace scripts, for example the icon shadows, the button borders etc.

@michelealbano
Copy link
Author

michelealbano commented Jun 12, 2023 via email

@ronso0
Copy link
Member

ronso0 commented Jun 12, 2023

Yeah, this may be due to the scour SVG optimization.

@michelealbano michelealbano force-pushed the main branch 2 times, most recently from 307bdb4 to 3de2963 Compare July 16, 2023 13:37
@michelealbano
Copy link
Author

michelealbano commented Jul 16, 2023 via email

@JoergAtGithub
Copy link
Member

Link to new PR: #11747

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

Successfully merging this pull request may close these issues.

4 participants