4 ms·
There are so many helpful node workflow conveniences that there really needs to be a standard for them IMO. Otherwise the default is to start with a layer of un
by themodelplumber 4y ago
There are so many helpful node workflow conveniences that there really needs to be a standard for them IMO. Otherwise the default is to start with a layer of unnecessary tedium around the flexibility.
Something like an AI coding partner would also be super helpful with nodes, eg "suggested pattern: you're recreating this common image editing filter or one of these variations" and boom, all the connections fall into place.
(Dragging connections across the screen is fun until it's the same lines most of the time...have used a lot of different node workflows over the years)
Also I'm still hoping for a generalized node workflow desktop...but I guess I might settle for a text editor.
For example you see nodes for a timer/cron job to generate the first part of your markdown --> text editor node with your template (into which a markdown highlighting plugin is also plugged) --> Pandoc node --> separate nodes for HTML, LibreOffice output filtering --> (LO as a node would be cool btw) --> SSH file transfer (HTML) and Email (to someone) nodes --> various inputs to those, etc.