The Dataflow.Blueprint layer now offers some limited dataflow network modeling via a BGL graph, and some basic runtime reflections for classes that model the Component concept.

The following features are planned for the future:

  • Serialization - It should be possible to serialize and deserialize a network blueprint. This could be used to store dataflow programs, or to send them over the network.
  • Separation of network blueprint and network instance - Right now the network class serves both as a blueprint and as an instance of the network. These two will be decoupled in the future.
  • Dataflow support layer - Dataflow.Blueprint ports, components and networks should model the generic dataflow concepts. This will allow the use of the common syntax, as well as the creation of blueprints of blueprints :-)
  • Python bindings - runtime configuration and operation of networks using Python scripts.
  • Documentation - non-existant at this point...