On Tuesday, April 18, 2017 at 7:06:08 AM UTC-5, john lunzer wrote: I think if I *were* going to try to coerce you into anything it would be in > reviewing the boundary between Leo's core and Leo's Qt interface to ensure > that it is fully generic/decoupled >
Imo, it's decoupled enough. All, or almost all, of Leo's core interacts with the gui via the high-level interface. See leoPy.leo#Code-->Gui base classes-->@file leoFrame.py-->API classes-->class WrapperAPI and leoPy.leo#Code-->Gui base classes-->@file leoFrame.py-->API classes-->class TreeAPI A curses gui for Leo that implemented these APIs would be pretty complete. Of course, there are other issues, namely implementing some kind of event structure. The redraw_after methods may be the biggest hack. They are a performance optimization, and like many optimizations can be difficult to understand. I have no opinion about whether they all could be replaced by a full redraw. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
