> > I have always thought it rather puzzling to have self-contained themes and > then an entirely different way to set fonts. > My preference is to set everything related to UI in the theme. >
I agree, all UI elements should be in one place. However people shouldn't have to wade through tons of nodes to adjust basics like font-size and -family. A convention to always have these as cloned nodes at the top of the theme.leo would help. For all-ui-in-theme approach the menu "Settings >> Edit Settings >> ***" would need to copy to the active theme instead of myLeoSettings. (Maybe not a significant barrier; I don't know.) The cascade of "Settings >> My Settings >> This Leo File Settings" is a core principle and applies to just about everything. I think we can/should use this in UI as well. Theming confuses things because it's off to the side somewhere and isn't clear (to me) where it fits in the cascade. Blue sky: I'd like to be able to run `show-settings` into a Leo panel, that has a filter category buttons plus a text field at top. From there I could 2x-click or [enter] on any given setting and be taken to the location where that is currently defined (LeoSettings, myLeoSettings, MyCoolTheme.leo, ThisLeofile.leo). At which point I could change as needed. If this place happens to be a System setting (not mysettings or local leo file) then my changes are saved/moved to the next level down. (Or answer a prompt which asks at which level to save the setting.) -matt -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f0e1efe7-c124-4cc8-adc3-c3f96ce99e7f%40googlegroups.com.
