Ryven

Ryven now includes a complete integrated python interpreter.

- It is a fully functional REPL so you can do anything you would do in the normal python console
- You can add references to individual nodes, by right-click operation, to access their full API in the console
- All print() calls, exceptions, and debugging messages are automatically redirected to this console

This is going to be one of the major features in the future, the possibilities are endless.

Some major additions and improvements, besides better examples/nodes. In particular:

- new linalg package containing nodes representing most basic matrix operations with nice interface
- two new designs
- heavy improvements in the appearance of source code files, which makes programming nodes much cleaner
- new variable update system: you can now create connections between script variables and methods, so that every time the variable changes, the connected method gets called - which enables much more responsive components that automatically adapt to change of data
- a matplotlib example node
- new internal design management system, it's easier now to create new designs, so there might be a few incoming
- passive mode for set var node
- and a long list of small fixes and improvements

The release also includes a prototype for a new tool (currently referred to as *Ryven Console*) to run a Ryven flow on the console, completely without GUI dependencies, with much higher performance which might become important for larger performance-intensive data processing tasks.

One major internal change: the default imports in custom NodeInstances and their widgets aren't done manually anymore. There are now two *env* files that automatically import all requirements when Ryven is running. This is much better as it ensures that the import list is always up to date. I updated all existing nodes' imports.

They work for data as well as execution connections. In exec mode, they also serve as sequence nodes, so you can dynamically add exec outputs that get executed from top to bottom sequentially.

Using a new viewport update mode feature you can now make a flow update the views of nodes when they get updated, even if the flow isn't fully finished with the current execution. That's really useful for larger pure data flows doing data processing (like in the OpenCV example, try it there). Furthermore, Flows now have their own settings which get saved and loaded to and from project files to choose an algorithm mode and the new viewport update mode. Also, I added a small 'bubble sort' example and some basic nodes (there are still quite a few missing, though).