​On Mon, Mar 5, 2018 at 10:42 AM, Terry Brown <terrynbr...@gmail.com> wrote:

A reason to retain single use @ constants would be allowing users to
> change things by editing a single setting, rather than having to grok a
> Qt stylesheet.
>

​This will always be a judgement call.  However, this question is *almost*
moot because in the new scheme my first stop is *always* the relevant css
node in the @data qt-gui-plugin-style-sheet tree.  This ends all confusion!

Starting with a *smallish* Qt stylesheet, it is easy to grasp what is
intended. I see all and only the @ constants that apply to that particular
css. From there, it is easy to find @ constants by looking at the theme's
settings tree.  In this case:

   leoSettings.leo#Themes-->@theme Leo Solarized Dark-->
   Settings for Leo Solarized Dark theme

This tree contains just a few, easily understood, categories.

I only understood the importance of *starting with small bits of css* as I
was writing this reply.

Take a look at @theme Leo Solarized Dark.  I think you'll see how simple
everything is.  Of course, css is inherently picky.  Chris George did a
great first draft.  I've done a lot of polishing.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to