On Tue, Feb 14, 2012 at 6:29 AM, Edward K. Ream <[email protected]> wrote:
> Work continues. As my brother would say, slow but slow.
I've just seen how to take smaller bites of the elephant.
The Aha is this: there are two parts of the LoadManager class:
1. The part that controls the overall load process. This is the
analog to the run() function in runLeo.py.
2. Various components that init settings and do other "smallish" tasks.
I can develop the pieces of part 2 without using part 1. Indeed,
specific parts of Leo's existing code can call parts of part 2 now.
For example, I can change the *existing* doPrePluginsInit in runLeo.py
as follows:
if g.new_load:
g.app.lm.readGlobalSettingsFiles(file)
# reads only standard settings files, using a null gui.
# uses files[0] to compute the local directory
# that might contain myLeoSettings.leo.
else:
g.app.config.readSettingsFiles(None,verbose)
for fn in files:
g.app.config.readSettingsFiles(fn,verbose)
Imo, this kind of strategy is essential in order to manage the
complexity of the required changes. There is simply no reasonable way
to eat the elephant in a single bite. An incremental approach allows
me to do full tests after each of these smallish bites.
This will continue to be a slow, picky process. For example, there
will be ongoing issues of initing the LoadManager class while we
incorporate more and more of the LoadManager code into Leo.
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.
