Hi again, Thinking about it a bit more, I suppose there are two types of widgets to > consider. First are panels and buttons and such. Seems like these should > follow OS settings just as Firefox does. Can't think of a good reason not > to. > > Next, there are the areas where syntax highlighting occurs, which as you > mention become problematic. Unfortunately we are slammed here with work so > learning how and writing themes for every plugin to a tool we use is not a > good use of time. > For what it's worth note that Firebug is mainly done by volunteers working on it in their spare time. Of course it's not expected that people work on it during their normal work time.
> So, I'm trying to think up a "quick" way to mitigate the problem, and > these came to mind. > > 1. Have a menuitem that selects either light or dark value foreground > colors for highlighting which can be manually toggled to the one that gives > the best contrast. > The Firebug Working Group is currently working on integrating Firebug into the built-in DevTools, which the side effect that Firebug can reuse their light and dark theme. 3. Have a menuitem/checkbox to "just use the OS theme," unselected by > default, but let's the user choose their own destiny. > Ok, that's something that can be considered for the panel toolbars and buttons (but not the panel contents) as you say above. Sebastian -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/31ed598f-08df-4ed3-9e8d-7a75e76f491d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
