* Anton Aylward <[email protected]> [11-18-16 10:10]:
> On 11/18/2016 09:23 AM, Roman Lebedev wrote:
> 
> Please don't CC me, I subscribe to the list and by cc'ing me I end up with
> duplicates.
> 
> 
> > On Fri, Nov 18, 2016 at 5:17 PM, Anton Aylward <[email protected]> 
> > wrote:
> >>
> >>> Gtk3 uses css theming.
> >>> Since dt 2.0.x, we use gtk3.
> >>
> >> OK, so what d I do to transform my old Gtk2 file into a Gtk3 one
> >> that darktable > 2.0 can use?
> > No idea to be honest.
> > Gtk3 breaks css theming every release.
> > 
> > I'd copy share/darktable/darktable.css to ~/.config/darktable
> > And edit it.
> 
> OK, done that.
> I also changed the couple of entries that I could find correspondence with
> 
> 
> @define-color bg_color #3E9B16;  /* was #212121; */
> @define-color selected_bg_color #0D4ED1;  /* was #353535; */
> 
> But its still a bit rough and I have no idea what the various CSS stanzas
> correspond to.  That makes it difficult to fine tune.

doesn't make much diff, as it will break with the next gtk3 update :(
 
> I also not that there are some embedded color values in addition to the ones
> defined at the top of the file.
> 
> Even so, it seems the scroll bars are narrow, or are, if the comments inline 
> are
> true, very wide.  They also lack end arrows.

panels too narrow ???

> Perhaps there's no cross-browser CSS for end arrows, but there is the
> GT3-theme-engine so perhaps that can do it?
> 
> Hmm,  How can I make darktable simply follow the selected GTK3 theme
> 

seems to be rather useless endeavour unless you feel somewhat masochistic.

-- 
(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
Photos: http://wahoo.no-ip.org/gallery2      Registered Linux User #207535      
              
Photos: http://wahoo.no-ip.org/piwigo            @ http://linuxcounter.net
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to