On Tue, Nov 19, 2013 at 9:17 AM, Fidel N <[email protected]> wrote:
[snip] Traversing Leo outlines is not, in itself, traumatic. Many people are familiar with outlines, even if they aren't familiar with all the data in Leo's settings trees. > The buttons of such gui should be able to change a few basic things from > Leo without the user needing to edit any outline. > You have said the magic word. The birdie descends. Boy, does that date me! There is no way I'm going to do any gui-based version of Leo's settings, unless possibly the gui itself is generated by those same settings. In theory, this could be possible, in practice, it would require an amazing command of various Qt layout classes. I'm not going there. The Find pane is enough! But "buttons" is the magic word. We could use @button nodes to munge on settings. Naturally, this should be done in myLeoSettings.leo. This meshes well with the wishlist bug of creating myLeoSettings.leo automatically if it does not exist. This default myLeoSettings.leo file would be a copy of a template file in leo/config. This template file could have all the @button nodes we could want. It's an easy, flexible plan. So, lets take body font size as an example: > A button from that gui could offer a size picking, then when picked, go > find the leosettings node that has the font size of the body, and replace > it with the new value. > Same for the few very important settings every noob wants to configure, or > for the few settings we would like noobs to be able to access early on. > Yes! Replace "button from the gui" by "@button script" and we agree completely. A great suggestion. Leo must have this asap. 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 [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/groups/opt_out.
