> > 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. >
So, essentially take the live settings after all the startup processes have completed and save that state on disk somewhere? With g.app.db being the "somewhere"? I guess this is fine if we trust that g.app.db is never changed outside of the "save settings" command. Otherwise, as I'm conceiving of it, this scheme would then also need a mechanism to compare the saved state with the settings .leo files, which would blow any performance gains, and add complications of what to do when sometthing differs. Hang on, I've just described a cache. I don't think that is what you're pointing towards, because that wouldn't make finding and changing the setting currently of interest any easier. 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/0ab2e76b-bf8f-49c4-9398-f4568ac7d1b0%40googlegroups.com.
