The goal here is to make Russ's internal event model easier to understand, to enable easier understanding and contributions from other contributors (i.e., not me) by converting Russ's internal event model to be more like a curtailed version of The Elm Architecture ("TEA" for short).
The idea is not to copy TEA entirely (as the view code remains mostly unchanged) but to make the message/event handling easier to untangle.
There is more that we could possibly do here, to maybe introduce a notion of a Command, that performs and side effects like HTTP requests, database interactions, UI draw, etc., but that would be a much bigger change and I'd like to try this change first before moving forward with anything more ambitious.
This is also just a medium-sized refactoring, with some functionality moved around to hopefully make it clearer.
The goal here is to make Russ's internal event model easier to understand, to enable easier understanding and contributions from other contributors (i.e., not me) by converting Russ's internal event model to be more like a curtailed version of The Elm Architecture ("TEA" for short).
The idea is not to copy TEA entirely (as the view code remains mostly unchanged) but to make the message/event handling easier to untangle.
There is more that we could possibly do here, to maybe introduce a notion of a Command, that performs and side effects like HTTP requests, database interactions, UI draw, etc., but that would be a much bigger change and I'd like to try this change first before moving forward with anything more ambitious.
This is also just a medium-sized refactoring, with some functionality moved around to hopefully make it clearer.