Divooka Engine

Divooka engine is our custom node-based visual workflow framework that allows everyone to develop and ship their own visual node editors. If you are looking for creating custom distributions with specific functions and do not interact with the rest of the Divooka eco-system, e.g. for domain specific use. Then this is for you.

Divooka Engine is available on Windows at the moment but Mac and Windows will be supported when full version is released.

Plugins

Extension of the Divooka Engine is primarily achieved through plugins. Although one can also use scripting to automate certain aspects of Divooka graph editors.

Plugin folder structure:

/Plugins
	/<PluginName>
		/<PluginName>.package.yaml

YAML file format:

Identifier: <PluginName>
Display Name: <Plugin Display Name>
Entry Assembly: <Assembly>.dll

At the moment there is no way to override plugin search paths - support for it is planned.

Plugin Debugging (Visual Studio)

(Pending tutorial)

The --debug flag of Neo allows plugin debugging in a different scenarios, by searching within current folder for plugin entry assembly.

Below are the few different ways to debug plugins (make sure we use Debug profile to build things):

1. Manually copy files into Plugins folder, then either start Neo directly (with project loaded in solution, if one has access to Neo source code) or use Attach to Process (or Executable debug profile).
2. Use --debug with a (single) plugin metadata file (either matches folder name or not), works in Attach to Process (or Executable debug profile)
3. Use --debug and working directory . assuming plugin project name is same as assembly name, works in Attach to Process (or Executable debug profile)

NuGet References

All Divooka packages are published on NuGet when available.

Prepare a local NuGets folder and use local NuGet feed for easier debugging, which allows debugging of direct project reference despite using NuGet PackageReference.

References

• Checkout the tricks
• Checkout a useful tip on Factory Pattern