D24122: [GTK3] Generate Breeze Light assets

[Carson Black]

cblack added a comment.


  In D24122#561773 <https://phabricator.kde.org/D24122#561773>, @ngraham wrote:
  
  > Conceptually it seems like there are two ways to go:
  >
  > - Have a single Breeze theme that always follows the color scheme
  > - Expose the ability to force the use of a particular color scheme via some UI (for example adding "Breeze Dark" and "Breeze Light" themes that always use the colors of the color schemes of the same names).
  >
  >   But I think it will be terribly confusing if we add themes that *only* hardcode the colors of certain elements like checkboxes and windeco buttons. It should be all or nothing IMO.
  >
  >   One alternative UI for this that I've been tinkering with in my mind is as follows: We have only a single "Breeze" GTK theme which follows the color scheme by default. Then there's a "Configure" button that lets you tell the theme which color scheme to use, with the list populated with all the installed color schemes, and defaulting to "Use system color scheme".
  
  
  I'm talking about a more technical difference that would allow said themes with 100% hardcoding to exist without duplicating the entire set of stylesheets for each theme.
  
  Basically, GTK will always read the user's gtk.css and will always load the colour definitions, always overriding whatever is in the theme.
  
  I'm looking for options that will allow themes to not get their colours overridden, but as I said...
  
  > I can't get any answers about things necessary for alternative methods

REPOSITORY
  R98 Breeze for Gtk

REVISION DETAIL
  https://phabricator.kde.org/D24122

To: cblack, #breeze
Cc: ngraham, plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, fbampaloukas, GB_2, ragreen, ZrenBot, alexeymin, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20191112/e9e14f1e/attachment-0001.html>