yeah, let's talk it over tomorrow?

sure

i should be up early tmrw

I think I'll start with that alias thing

cool

whats your plan in terms of splitting time btwn this and config editor

I'll do this first

cause schema changes

perfect

makes 100% sense

ok, first attempt was kinda failing

or like, a bit too lazy

but yeah, I got it now

?

approached the naming of stuff within pipelines wrong

started second attempt

it's okay :)

oh cool!

@freiksenet i’d love to see where you ended up

I've ended up deleting version 1,so there almost nothing ready in version two. in one I tried to rely on dicts, and then just use keys as aliases, but backportibg stuff proven hard. now I think I'll have a separate entry like PipelineSolid which will have name and definition fields and I'll make everything work on that

otherwise too much code relies on solid having name

eg multiple places construct by name dicts

sorry, it wasn't the most efficient day 😆

k

hey guys! just a quick update—I’ve updated the DAG to flow top-down (still using dagre for the node layout and SVG / foreignobject for rendering) and I’ve got it looking pretty nice. I think this layout is definitely easier to follow since it accommodates the long text better. I’m not super happy with the current stacking of inputs / outputs (with the connection points being the left edge) since it makes the edges a bit hard to follow when there’s more than one, so I’m playing around with a few variants of that

lemme know what you think

this looks awesome

I think maybe we should use dagre for links too, atm I'm just ignoring link data from them

(here’s one where the edges are especially tough to see)