Karsten Schmidt

Yeah, I don't know how to get this work either, but am sure it's possible. Need to study @jashkenas' input widgets. Anyhow, forked your latest and made some interim updates:...

Okay, one hack later and I've got a version which kinda works (incl. undo/redo history of user interactions). Didn't fork, just updated the same notebook: https://beta.observablehq.com/@postspectacular/thi-ng-umbrella-scaffold-w-hdom-context

I see where you're going here :) You're also right that transducers are not v. suitable (or even meant) for branching dataflows, but they're great for linear pipelines. That very...

Great! There's definitely some food for thought here, but since this example conflates quite a few different concepts (time, composability, topology order) I can't think of a more straightforward solution...

Hey @den1k - here's a preliminary version of the preliminary-named `mapTopo` transducer, which I think kinda does what you're after. Similar to the graph setup it takes an object of...

Am not entirely sure I follow these latest points. Can you please clarify why `close` would not be defined here? ```js delta: { ins: ["close"], //

It's actually not all quite like that at the moment. The `compileXform` converts a spec like this: ``` { ins: ["foo", "bar"], xform: tx.map(({foo,bar}) => foo + bar) } ```...

Hi @miraklez - am moving house this week and alas can't look into this right now. will get back to you asap (next week some time)

Just a quick one: There's a 3.5 year old branch for async transducers. I stopped with it due to widespread lack of async/await support back then. I've been meaning to...

Sounds reasonable, @dazld - I might not have bandwidth to work on this until mid Oct though, but will try...