It seems like Leo is doing way too much work. Why should Leo load local files twice?
When loading a local file, say x.leo, the sequence would be: - Read settings in leoSettings.leo and myLeoSettings.leo as needed. - Load the data in x.leo. - Create c and c.config and all the other objects, thereby creating the visible outline. - Scan settings, thereby enabling plugins enabled in x.leo that have not been loaded. - Run the "after load" event handlers as usual. Loading another local file, say y.leo, would work the same way, except that Leo would not read leoSettings.leo and myLeoSettings.leo again. I don't see any reason why this wouldn't work. I suspect the present double-load of x.leo happened because there used to be more than one possible gui. But even if there were multiple guis, the user can, and probably should, enable the desired gui from the command line. If that isn't convenient, the user could enable the desired gui in myLeoSettings.leo. In short, loading .leo files once seems feasible. It would simplify Leo and speed loading. However, my fear is that the new load sequence would "break" outlines by changing how they load. So it would seem prudent to enable the new load code with a global switch. We can then easily back out of the new code if it causes any problems. Your comments, please. Edward P.S. Loading .leo files once would immediately solve the problems with c.hash() and disappearing settings. The hard "linking" problem would disappear because for each x.leo, there is only one copy of the c.config object. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
