On Sun, Jan 5, 2014 at 6:38 AM, Edward K. Ream <[email protected]> wrote:
> I plan to complete the code and integrate it into the @auto read/write > code today. > Done. As stated earlier, I plan to use @auto to generate leoViews.py itself. > Done (on a copy of the file). This revealed one last complication, which I have been working on all day, namely properly creating all organizer nodes, especially nested organizer nodes. Clearly, this is doable: the @organizers tree contains all necessary data. Doable, but very tricky. The problem is that the @organizer: nodes contain full unl's of child nodes, but those unl's are invalid until we create the organizer nodes, which is what we are trying to do! This is the kind of problem that demands my complete attention. I'll be mostly incommunicado until I get the job done... Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
