On Wednesday, May 10, 2017 at 3:25:32 PM UTC-5, Edward K. Ream wrote: Please note, everyone, that there is a *lot* of work still to do: >
As mentioned in a recent Engineering notebook post, the next phase involves having the drawing code understand (or generate) wrapper widgets for headlines. I am now in what I call a "wrestling with code" phase. It's definitely a physical process. I also think of it as sculpting clay. Leo is the perfect tool for this kind of thing. I can copy/paste code from npyscreen classes for reference while working on subclasses. The goal is to use Leo's existing vnode structure instead of the corresponding npyscreen TreeData objects. Clearly, the goal is feasible. Leo's tree resources are far richer than npyscreen's. In practice, only the LeoMLTree.update method will change, so the task is in some sense bounded. But this task is not straightforward. I am in the process of "unwinding" the twisty little maze of calls to adapter methods in the MLTree class. This unwinding process will simplify the code and deepen my understanding of what *exactly* is going on. As the code gets simpler the way forward will start to emerge. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
