Clojurians Log v2

Interesting phenomenon: mxFlutter now has four Matrix-based ways to deliver Flutter components and can deliver Flutter components developed with raw Dart or via alpha/widget, and can deliver a single app involving any combination of all those at the same time. The only limitation is that non-MX widgets cannot own MX-widgets. I am not used to disparate frameworks happily coexisting. One of the MX delivery methods, the one based on a layer of deftyped widget wrappers, is doomed, I think, by the boilerplate of the deftype. The latest delivery method is a bit scary: one cell generates the state, another cell generates the widget reading its state from the other cell -- seems like overkill, but one thing Cells does is get things to run in the right order and JIT if we make them lazy, so it is kind of perfect. Cells also has a disposal subsystem so it would also help avoid leaks. OK, talked myself into continuing with the latest approach, on branch "take3".