-
Notifications
You must be signed in to change notification settings - Fork 189
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
Create Color Definition for Reuse #2455
base: master
Are you sure you want to change the base?
Conversation
I only tested on macOS. |
Test Results 1 821 files ±0 1 821 suites ±0 1h 51m 58s ⏱️ + 4m 0s For more details on these failures, see this check. Results for commit 2dd4a45. ± Comparison against base commit 4fbbe1b. ♻️ This comment has been updated with latest results. |
With 845377a this issue is fixed. |
This pull request changes some projects for the first time in this development cycle.
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patch
Further information are available in Common Build Issues - Missing version increments. |
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.
Are we somehow committing to the id of the definition org-eclipse-ui-workbench-SECONDARY_BACKGROUND
and have to keep it stable?
I guess with the latest hidden
flag, we can consider this ID to be purely internal and should be able to rename this?
I would say we can consider it internal as it only appears in the CSS files. Anyway: Do you have a better name? |
👍
No, hence the question 😉 |
I think it is great to allow the user to change the default colour. I think it should be relatively easy to implement that colors refer to others in CSS. What exactly is the requirement here @BeckerWdf ? |
Color and Fonts can be defined as not editable if done via the extensions point. Provide the same possibility if they are defined via CSS.
What I want to do is this:
instead of:
@vogella: Would be great if you could help here. Feel free to push a separate PR / an additional commit to this PR |
Instead of writing the same RBG color codes over and over again in various places in the CSS files only do it once.
Define a new color and re-use that color definition at all other locations. This also adds a semantic name to the color code.
Unfortunately color definitions cannot refer to other color definitions. So at some places we still have to provides the color code. These places are marked with a comment.
The new defined color is now also visible in the "Colors and Fonts" preference page. I am unsure if this is something we want. If users change this this does not work 100% because of the limitation above.