We could use some documentation. The examples certainly help, but I found that once I started trying to do more complex things, I ended up having to dig into the source code to understand how to use this library.

GitHub has a feature where each repository can have a website. Maybe we could set up the documentation there? Or maybe we could use GitHub's wiki feature?

I know you guys are focused on bringing more features to the lib, but it would be good to provide a bit better documentation and examples (I sent another post about this), so the ones willing to use the current version can fully understand what they can do with it..

E.g.

• I am not sure how to use signals, I can see raft::fileread uses raft::eof, but not sure what is done with it.
• I don't

I have disabled the PDF builds after merging #3124. It is probably something easy to fix, but is there a strong reason to keep building the PDF output?

in example topolopy, when i execute "clear Graph", the message show "TypeError: Property 'clear' of object qan::FaceGraph_QML_70(0x7884400, "graph") is not a function",so i modify "void clear() noexcept;" to " Q_INVOKABLE void clear() noexcept;" in the file "qanGraph.h" 103 line ,but that still error.

May be it's finally time to split things in modules and separate files, even the tiny ones. So rewriting it in TypeScript or smth. would be much easier and code will be even easier to parse and test.

Needs updating to reflect current status of Calvin.

Currently it is possible to create custom nodes, it is not yet documented.

Create a page with an example that implements the node described here: fibo/flow-view#60

DtCraft has a built-in reactor for event-driven programming. We will add a chapter discussing the basics in our cookbook.

Make the initial setup of UQ scripts easier, by inputting various paths and parameters using SCIRun first. This could even run a few examples of what the toolkit can do as well.

Add classic hello world to dflow examples: found it here https://nodejs.org/en/about/

const http = require('http');

const hostname = '127.0.0.1';
const port = 1337;

http.createServer((req, res) => {
  res.writeHead(200, { 'Content-Type': 'text/plain' });
  res.end('Hello World\n');
}).listen(port, hostname, () => {
  console.log(`Server running at http://${hostname}:${port}/`);
});

We will probably have to do this sooner or later, although the style may not fit well to document individual PipeOps.

Feature request
Sometimes we'd need random behaviours to work, so we'd like to have a Random node.

Solution
Having a node that allows an output randomized between a mix and max value.