3 ms·
Thanks for sharing this, awesome project. The feature set looks pretty comprehensive from the screenshots. Is there a way to export the created canvas from the
by mjgs 6y ago
Thanks for sharing this, awesome project. The feature set looks pretty comprehensive from the screenshots.
Is there a way to export the created canvas from the editor?
I’m imagining a workflow where people/teams create the RSS processing canvases and then share them using an export.
Also is there a CLI tool?
- onli 6y agoHey, thanks :) The project's web application is currently not separated enough into backend/frontend to forge a CLI tool from that backend. There is an export function, but it's meant as a data export for all the pipes (to not hold data hostage), not per canvas, and to my knowledge no one so far has tried to work with the JSON representation the site exports. However, you can fork pipes in the site UI and then edit them like that. And if a team would share an account to manage a set of Pipes together there is nothing that would prevent that.
- mjgs 6y agoThanks for the details. The sort of thing I was thinking about was something similar to how post production workflows are setup in film vfx. You have teams of artists working on 2d and 3d software packages locally. They then save their project, which produces a file that can be rendered on the render farm. In this rss news equivalent, teams could mash together RSS feeds. Then send their local project export to a backend infrastructure, that would do something with the export, maybe generate a static site, or something more complex .
- onli 6y agoI mean, RSS fits well to prepare data to go somewhere. Just the offline part you probably do not need. Create your pipe, share the account, or let the other developer fork the pipe. The tool that in the end consumes the feed can just work with the online feed directly from Pipes - those tools expect an url anyway.