On 11/19/2013 9:07 AM, Edward K. Ream wrote:
In the spirit of simplifying everything for new Leonistas, I propose
the following guidelines for the content of leoSettings.leo:
- No clones.
- No disabled nodes.
- No scripts except possibly @button buttons to help newbies.
Certainly no developer scripts of any kind.
- The "Startup" node should explain itself and tell new newbies not to
change its contents.
- The "About this file" node should have the clearest possible
directions, with a link to a screencast, and a proper discussion of
myLeoSettings.leo.
The "simple things are too hard" attitude is a revolution:
- Before, I would have said that clones make it easier to access
settings. They do, but only for experts.
- Before, I would have said, let's put lots of disabled settings in
leoSettings.leo. Fine for experts; bad for newbies.
I'll put these guidelines in place today. This will entail creating
leo/config/settingsExamples.leo There will be no @settings node in
this file, so there will be no need to disable any setting there.
Terry, any comments? Anyone else?
Edward
Just one request:
For *each* plugin that grabs config settings (@bool, @string, etc), be
sure to include the *default* settings, even if your code is smart
enough to work without it. I already do this with my plugins, as it
helps the users understand the settings better, I feel. Be sure to use
the node bodies to describe what the settings do, and what the default
value is.
-->Jake
--
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
