On Fri, Mar 10, 2017 at 4:26 AM, Edward K. Ream <edream...@gmail.com>
wrote:
I am about to refactor Leo's the @theme trees in leoSettings.leo into an
> unchanging *base *part, and a few *overrides *for each theme. Themes will
> be defined by their overrides.
>
Done at d6ac525. After a few false starts, a simple, safe way forward
became clear.
1. Deprecate the three existing "leo dark" theme, now in
leoSettings.leo#Themes-->Deprecated themes
This node explains why the themes are deprecated. There is no great reason
either to use these theme or to remove them ;-)
2. leoSettings.leo now contains two new themes:
- @theme base dark theme
- @theme windows ekr dark theme
The latter theme contains just a few overrides of the former. All
overrides are marked with zz, a hint that they must be the last child of
their parent.
Folks, this is a giant step forward. For the first time ever we can
distinguish between common settings and per-theme settings.
This is a completely safe improvement. The old themes still exist, but
nobody is likely to care. Existing users will continue to use whatever is
working in myLeoSettings.leo.
Edward
P.S. In leoSettings.leo the "base dark" theme is included, via clones, in
the "windows ekr dark" theme. As a result, changes made *within
leoSettings.leo *to the "base dark" theme automagically become part of the
"windows ekr dark" theme.
Naturally, once one or both of these themes is copied to myLeoSettings.leo,
the clone links are broken. This is not likely ever to be a problem
because we don't ever expect the base theme to change.
EKR
--
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.
