<table><tr><td style="">ndavis added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D25814">View Revision</a></tr></table><br /><div><div><p><a href="https://phabricator.kde.org/p/hpereiradacosta/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@hpereiradacosta</a>, Fair points and I'm glad you spoke up. JFYI, I'm in no rush to land this and I will consider reserving this change for KF6 if experienced KDE devs think that is best.</p>
<blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D25814#574105" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D25814#574105</a>, <a href="https://phabricator.kde.org/p/hpereiradacosta/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@hpereiradacosta</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>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.</p></div>
</blockquote>
<p>In terms of breakage, I think it would be fine if I made the color fallback (as you said) to what the breeze widget style currently does. 3rd party widget styles wouldn't use this color without modification, so it shouldn't hurt them. KColorScheme already has default colors, but they're defined before KColorScheme tries to read colors from the colorscheme file instead of when a color is not found. That hurts the flexibility of these defaults and seems backwards to me, but there may be a reason for it that I don't know of.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>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.</p></blockquote>
<p>Yes, it is yet another option in a sea of options, many of which are completely useless when a user ventures outside of the Common Colors section. You're probably correct that most users don't even bother with manually adjusting colors since choosing good colors can be tricky. I don't think that makes this option useless though, except for the fact that it's repeated for each color set and only a few versions of it will get any amount of use. I hope to simplify the colorscheme editor in the future so that only options that do something are exposed.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Or do you plan to ship a "breeze dark with dark separators" +and+ a "breeze dark with light separators" ?</p></blockquote>
<p>I do not.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>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 ?</p></blockquote>
<p>There is no such poll.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R265 KConfigWidgets</div></div></div><br /><div><strong>BRANCH</strong><div><div>separator-color (branched from master)</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D25814">https://phabricator.kde.org/D25814</a></div></div><br /><div><strong>To: </strong>ndavis, Frameworks, VDG, dfaure<br /><strong>Cc: </strong>cfeck, hpereiradacosta, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns<br /></div>