On Sunday, July 9, 2017 at 2:15:06 AM UTC-5, Edward K. Ream wrote: > > >> On Wed, Jul 5, 2017 at 3:51 PM, Terry Brown <[email protected]> >> wrote: >> >>> I'm wondering if it would be a useful thought experiment to list a >>> series of "run levels" (https://en.wikipedia.org/wiki/Runlevel) or >>> levels of initialization for Leo - just a textual list where we do our >>> best to be aware of dependencies for each level. >>> >> >> It does seem that a more orderly, official and documented startup process >> would be beneficial in many ways. >> > I keep coming back to this idea. Keeping details deliberately vague, the startup process might be something like:
1. Init the most basic vars, and do the most basic imports. 2. For each loaded file, init *all* of Leo's settings, using sqlite and maybe a new "minimal" Commands class to read settings files when necessary. 3. Everything else. That is, create a commander for each to-be-loaded file, init the commander thoroughly, and create the outline from sqlite or the actual external file. This is pure speculation. I may be relying on sqlite for too much magic. Hope not. As more magic, it would super if we could get rid of caching entirely... Edward -- 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.
