On Apr 24, 12:24 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > Work continues with no major surprises.
This morning I began the transition to the sax-graph world by using the sax-graph code to edit Leo itself. This showed several easily- corrected problems. It was also the reason why I want to abandon the 3.x read code in leoAtFile.py. That code is now gone in the sax-graph branch. I added new tests to the check-outline command, which promptly failed in an interesting way: the read code (both in leoFileCommands.py and in leoAtFile.py) did not properly put all cloned vnodes in the children lists of *all* their parents. I hacked a fix for this in both places. The check-outline command and the unit tests should really test *all* required data-structure constraints. The present tests may suffice, but that's not yet clear. Complete tests will make me feel a lot safer. For the next few days I plan to do many long-delayed cleanups of the code. This will give me a chance to test Leo more thoroughly with the new code. The grand merger of the sax-graph branch with the trunk is likely to happen this week. However, I would not recommend using the sax-graph branch just yet... 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 -~----------~----~----~----~------~----~------~--~---
