TiLiA uses the subscriber/publisher pattern to reduce coupling between objects. It's main implementation is in the "requests" module. Some classes, like TimelineUIs, work like "routers" of requests, they listen for them and call the appropriate code on instances of other classes. Because of that, they may end with a lot of subscriptions (which are done via the listen and serve functions). It would be good to refactor those subscriptions to be in a separate function instead of in the __init__ method if possible. As a bonus we could do that to other classes as well.
TiLiA uses the subscriber/publisher pattern to reduce coupling between objects. It's main implementation is in the "requests" module. Some classes, like TimelineUIs, work like "routers" of requests, they listen for them and call the appropriate code on instances of other classes. Because of that, they may end with a lot of subscriptions (which are done via the
listenandservefunctions). It would be good to refactor those subscriptions to be in a separate function instead of in the__init__method if possible. As a bonus we could do that to other classes as well.