On Tue, 27 Jun 2017 06:54:30 -0700 (PDT) "Edward K. Ream" <[email protected]> wrote:
> On Tuesday, June 27, 2017 at 7:58:02 AM UTC-5, Terry Brown wrote: > > My interpretation of the proposal was a replacement of all @settings > > trees, not simply caching. > > That's a much harder sell, but I won't veto it until I know a lot > more. Ok - thought you'd already said there was no way of changing your mind on this ;-) > I guess a demo project could demonstrate the possible user interface > > A very hard sell. We already have a working user interface for > settings that supports of all of Leo's features, including cff, > clones, scripting API (generators, p.b, p.h, p.gnx, etc.). Which are mostly tools and concepts of no help to new users, who are most likely to want to be changing settings. > Let's start with the easiest, quickest prototype that could possibly > work. This will typically *not* involve programming. A brief > description along with some sketches would be a quicker and more > informative. That way, everyone, including myself, could more > clearly understand the potential benefits. I agree, wireframes (https://en.wikipedia.org/wiki/Website_wireframe) are a good place to start UI wise. But a large part of the proposal's benefit is in the non-UI simplification of @settings loading. import leo.core.leoGlobals as g config = g.config_for_outline("/path/to/somefile.leo") could create `config` which would be c.config before c is created. And without loading somefile.leo or mySettings.leo or any other Leo outline. The path to file parameter would only be used to get the outline's identity, needed for outline specific settings. The best way to represent outline identity is still unclear, start from what c.db does I guess, but that's minor. Cheers -Terry -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
