On Sat, May 13, 2017 at 8:35 AM, Edward K. Ream <[email protected]> wrote:
I am now in what I call a "wrestling with code" phase. > ​Good progress to report. LeoMLTree.update has been refactored within an inch of its life. As a result, I am much more comfortable with what is happening, and I also can see the dogs that aren't barking. The way forward is as follows: 1. Don't use *any* of the MultiLine base code for drawing the tree or keeping track of the contents of the tree. Replace all that with vnodes. LeoMLTree will see be a subclass of MultiLine, so as to have access to event handling, widget layout, etc. 2. There is no need for *any* persistent headline widgets! The reason is simple: the npyscreen code doesn't use widgets to draw outlines! 3. tree.edit_widget can just return a string wrapper every time it is called! This will be a subclass of StringTextWrapper in leoFrame.py. No need for any of the "association" dict used in the Qt gui code. All this will collapse the complexity of the tree code. The curses gui may soon be fully functional. 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.
