On Feb 12, 9:45 am, "Edward K. Ream" <[email protected]> wrote: > This post will be of interest only to those with a deep interest in > Leo's implementation. Feel free to ignore. > > Otoh, this post explains why progress on the grand refactoring now in > progress may be a bit "stately" :-)
Work continues. As my brother would say, slow but slow. I am working on two tracks: development of the LoadManager class and work (in Leo's existing code base) that will eventually result in reading Leo files only once. This will be a bit tricky if the standard settings files (leoSettings.leo or myLeoSettings.leo) appear in the list of files to be loaded. Here is the checkin log for rev 4983. This should be safe enough to use, but one never knows... leoApp.py: - Removed unused code from LoadManager class. - Completed LM.computeLeoSettingsPath & LM.computeMyLeoSettingsPath. - Replaced LM.computeSettingsPath by a single statement in LM.scanOptions. - Completed first draft of LM.readGlobalSettingsFiles: more work is needed. leoAtFile.py: - Removed ancient, unused, new_write constant. - Added several tests of g.new_load, whose effect is that atFile class will call c.config only int new atFinishCreate method. leoConfig.py: - Fixed an old bug in readSettingsFiles: config.updateSettings must be called *before* g.app.destroyWindow leoFile.py: - Refactored fc.getLeoFile using fc.readExternalFiles. - Renamed fc.open to be fc.openLeoFile and changed all corresponding calls. runLeo.py: - Connected the LoadManager class to the leoApp class. numerous files: - added class comments in headlines of ctors so it is obvious to which class a cloned ctor belongs. Edward -- 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.
