hpereiradacosta added a comment.
Adding new entries to the kcolorscheme should be done with a lot of care, because it could be seen as some sort of API break for existing colorscheme, as soon as you start using this color in the widget style: you would need a fallback implementation, for all the colorscheme in the open which do not implement this particular color. These kind of additions happened a lot whith gtk3 css style and resulting of overall unhappiness and distrust from theme/color scheme developpers. This also increases the complexity of the code and difficulty to maintain. Also I am not convinced about the usefullness of this option either, especially considering that tweaking the colorscheme in the systemsettings is already quite advanced configuration (I would bet that most users stop at switching between pre-made color schemes, rather than tweaking a particular one. This will get even less the case if you start implementing more corner case colors. Or do you plan to ship a "breeze dark with dark separators" +and+ a "breeze dark with light separators" ? All in all i would say that people (that is: active developpers and the very few that manifest themselves on developper/vdg channels) having different opinion is not a strong enough argument to expose such a low level tweaking to all. Or is there an actual poll that shows (on a larger data sample) that one really cannot decide between the two options ? My two cents. Hugo REPOSITORY R265 KConfigWidgets BRANCH separator-color (branched from master) REVISION DETAIL https://phabricator.kde.org/D25814 To: ndavis, #frameworks, #vdg, dfaure Cc: hpereiradacosta, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns
