On Thu, 6 Jul 2017 00:49:52 -0300 "Xavier G. Domingo" <xgdomi...@gmail.com> wrote:
> Thanks for the thorough explanation. But you don't need a GUI app to > read an XML, as you don't need a GUI app to read from an SQLite file. > I understand that you need to read all the settings files to be able > to fully initialize Leo, but you don't need (or should not need) al > Leo's machinery to read the settings files. Even if they are .leo > files. Clearly the part that needs to be changed is that "Leo needs > all of its power to analyze outlines with settings". It may be the > case at present, but it should not. I think you're right in that another option would be to use something like the leosax module that reads Leo outlines into a simple dict/list representation in a fraction of the time Leo usually takes to load an outline. Settings could be made available early by reading Leo XML with that. You'd still have to re-scan them later in init. to handle @buttons and @scripts, which need the GUI in place so they can act on it. But that's true of any system. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
