On Tue, 16 Sep 2014 06:07:53 -0700 (PDT) "Edward K. Ream" <[email protected]> wrote:
> 1. The first several pushes of leoSettings.leo will retain the > original @data qt-gui-plugin-style-sheet node (disabled) and any > settings that have just become no-longer used. Yes, it will be an > inconvenience for existing users to have to use different settings > names, but imo there was no real choice: it is essential that a > single, uniform, consistent set of names be used. Changing settings > names will not be all *that* odious because... This brings to mind the issue of different themes, e.g. the existing dark theme. It seems that each will define its own tree of settings, and the more they match between themes the better, but I don't think there's any necessity to make this matching rigorous in anyway. > 2. The new settings scheme will moot the need for leo10pt.leo, > leo12pt.leo and all the rest. Instead, all font sizes are now > defined in terms of three intermediate settings: @string font-size, > @string medium-font-size and @string small-font-size. Changing just > these three settings will suffice to change *all* the font sizes used > in Leo. Is there a @font-size-body = @medium-font-size @font-size-log = @small-font-size etc. layer? That seems important. > 5. Overriding setting using @data qt-gui-**user**-style-sheet. > > Using this additional style sheet probably should be deprecated. I don't think so, it's a low cost way for knowledgeable users to tweak things to their preferences. > Indeed, @data qt-gui-**plugin**-style-sheet now takes care to define > almost everything that any user would want to define. That being so, > myLeoSettings.leo should contain overrides of only the @color and > @string nodes in leoSettings.leo. There should be no need to use > @data qt-gui-**user**-style-sheet unless one wants to do something > very unusual. Like fixing the annoyingly bright arrows in a calendar widget etc. etc. - I think there are plenty of uses for -user- stylesheet. > Indeed, an interesting stylesheet question arises. Suppose, as is > the case, that in effect @data qt-gui-**user**-style-sheet is > appended after @data qt-gui-**plugin**-style-sheet. The question is, > what happens?? Does each selector in the user style sheet > *completely* replace the corresponding selector of the plugin style > sheet, or do only the individual fields of each selector in the user > style sheet replace the corresponding field of the selector in the > plugin style sheet. I'm sure it follows the HTML CSS pattern of only affecting the attributes it references explicitly, it would be useless otherwise. > P.S. Debugging this beast is really tricky. I suspect that the > reason that @color nodes did not appear to work for you (Terry) was > that there was some kind of confounding error in effect. This > happened to me for a time, but now @color nodes work again and I'll > be converting from @string back to @color where possible. Followed > by more debugging & testing, of course... Not sure if it was @color or @font nodes that weren't working, or both. Not really sure what they add over @string apart from some readability perhaps, I guess they're good for that. Oh, and as targets for a helper widget interface which uses the color / font selector dialogs. Cheers -Terry -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
