This will be an ongoing log of my work embedding Leo into pyzo. It is mainly for myself, but anyone is welcome to read.
Where the work will happen
My copy of pyzo.leo contains a live copy of all of pyzo's sources. I can change any part of pyzo at will.
Traces tell me the order in which things happen. Most of the work on this project will happen in pyzo.leo, with added support as needed to Leo's bridge.
Patching pyzo
All patched files must have access to a singleton leo_x instance of the
LeoInterface class. This class will provide access to Leo's bridge, and
do other chores.
Traces show that instantiating pyzo's MainWindow class in pyzo.start() causes pyzo to load all previously-loaded files. Therefore, I plan to patch necessary pyzo files/classes just before that point.
Edward