On Thursday, November 2, 2017 at 12:09:55 AM UTC, Martin Janiczek wrote: > > > 1. Is this a good idea at all? > > Having stacked a few programs together by hand, this strikes me as an excellent idea and one that is worth exploring.
One problem I had was with TimeTravel.program which I was wrapping a RouteUrl.navigationApp with. All the messages were then nested at the time-travel level, and its UI did not support nested filtering, so I could not easily filter out animation messages. It occurs to me that if each middleware knows about the next layer, and has wrap/unwrap functions for it, that it would be possible to have set up the time-travel layer to unwrap the nested messages, if I had such a system as yours. Would love to see what a navigation example looks like. Rupert -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
