Vitalije, On Sat, Aug 24, 2019 at 9:54 AM vitalije <[email protected]> wrote: [...]
> After editing settings in the myLeoSettings.leo or any other settings > outline, user should invoke a command to save settings. This command can be > executed automatically on each save. This command would read settings from > the outline and build settings dict as it is now done during the startup > code. The result set of settings can be stored in g.app.db for the next > run. During the startup settings can be retrieved from the g.app.db in one > line. This would require the least changes in Leo's code. However there > might be even a better scheme. Store each setting in the db table with the > following columns: > (name, level, filename, type, value) where primary key is (name, level, > filename). > Then c.config.get<type> can be changed to execute simple query from the > database selecting the value at the highest level for this outline. Leo's > defaults defined in leoSettings.leo should have level=0, myLeoSettings.leo > - level=1 and all other outlines should have level=2. > I remember an experiment to test whether accessing settings from db would > slow down Leo and result was that sqlite3 database would outperform Leo's > present config machinery. > Do you envision distributing the leoSettings.leo derived database with leo itself? Or do you have something else in mind? I was wondering how that first database of settings would be available at the time of leo first use. Brian -- 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/CAO5X8CwBe%3Duv5PgzW1A0f8y9mvvTwikqhva0Nhi5CVxCGh%3DZmQ%40mail.gmail.com.
