Refactoring probably means using signals

[Edward K. Ream]

Leo's code is a behemoth. Nothing we can do is going to drastically shrink it, or make it a snap to understand or change.

Imo, using Qt's signals more effectively is likely to be the best way to simplify Leo's code just a little bit.  This page explains the benefits.

Signals aren't a panacea. Understanding signals and their interactions isn't trivial.  However, cff <signal name> gives an excellent overview.

I don't have any immediate plans to use more signals in Leo.  However, I would welcome any experiments in this direction.

Edward

[Terry Brown]

When we talked about this previously I looked at

https://pythonhosted.org/blinker/  and it seemed quite good, trying to find it again I

also see

https://github.com/dgovil/PySignal

"A purely Python implementation of the Qt signal system with no QObject dependencies"

if you want to think about something that doesn't tie you to Qt / allows a null-gui Leo state machine kind of thing.

Cheers -Terry 

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c744c586-929e-4229-b2b0-9c4166d40eb1%40googlegroups.com.

[Edward K. Ream]

On Fri, Aug 23, 2019 at 9:23 AM Terry Brown <terry...@gmail.com> wrote:

When we talked about this previously I looked at

https://pythonhosted.org/blinker/  and it seemed quite good, trying to find it again I

also see

https://github.com/dgovil/PySignal

Thanks, Terry.  I've bookmarked both of these.

Edward