Okay then, since the scope is very limited this is a perfect strter bug PR 
I think as a mechanical engineer you’ll have no problems getting started.
Read https://github.com/mixxxdj/mixxx/wiki/Using-Git, clone mixxx/2.3 and create a new branch deere-highcontrast
. Since we#re talking about skin changes only you won’t have to deal with the precommit
actions much (if at all).
I agree the Fx paremter buttons can be bigger, so this would your first commit.
At that point you should open a PR on https://github.com/mixxxdj/mixxx targeted at 2.3 (you need to create a Github account for that).
If that went well, most of the ‘hard work’ is done.
Then look at the scheming in Shade skin as I wrote above. It’s pretty staright-forward if you ignore the <Filters>
sections.
No big deal to create two Deere schemes called Classic
and High Contrast
and no need to actually load additional stylsheets, just test if both schemes show up in the Preferences > Interface > Color Scheme combobox and can be loaded.
Then you can create an empty style_highcontrast.qss
and add your desired high contrast changes to overwrite the general rules from style.qss
.
Even though the change set is rather small there will probably additional changes necessary along the way. In order to keep the git commit history minimal I suggest you also take a look what git commit --amend
does and how git --fixup ...
and git rebase -i --autosquash ...
https://fle.github.io/git-tip-keep-your-branch-clean-with-fixup-and-autosquash.html