On Jan 27, 6:17 pm, "Edward K. Ream" <[email protected]> wrote: > On Wed, Jan 27, 2010 at 12:07 AM, zpcspm <[email protected]> wrote: > > - how should the user be notified if the global settings file has > > changed, > My "subconscious" solution has been not to change leoSettings.leo > unless absolutely necessary. That is, I make most changes in *my* > leoSettings.leo, and refrain from changing leoSettings.leo.
Here I particularly mean the situation, when a plugin goes official and is added as enabled by default to @enabled-plugins. Of course, you can ask developers to add a new plugin to their myLeoSettings for testing purposes and just "officially" add it to the global config file right before a new leo release. But if a new plugin goes enabled by default as soon as it is pushed into the trunk, that is more beneficial (especially Ville is being a big fan of this agile approach and it's a good thing for leo that he is insisting on this and is pushing the conservative users). All involved people can start using it without having to do any manual work in order to enable it. Unless an old myLeoSettings.leo doesn't override the updated global settings file, like it happened in my situation. I think this particular case emphasises a more general one. The global leoSettings.leo file has a specific status in the source code tree, that is slightly different. That's because of its link to myLeoSettings.leo, which is not a part of the trunk. I think this particular case also emphasises one more general case, that is totally unrelated. We've had countless talks and brainstorms concerning these settings issues. Lots of bugs were reported, lots of complaints were made. And you made a really huge effort to improve things and to make everyone happy by adapting leo's behavior to suit everyone's needs. Sometimes I think about this and I keep asking myself, maybe subsets of these problems are the consequence of some rigid design choice? By this I don't mean the overall leo configuration machinery, which is quite flexible. I mean just the particular mechanism of enabling plugins. They are all in the same node. This is quite rigid. They are described by a flat structure: the node body, which is just like a regular file, not a tree structure (oh yes, nowadays I'm a big fan of trees, I consider them being superior to flat files and spreadsheets, and this is because of leo). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
