Divooka Distributions

Every Divooka distribution is the same language running on the same runtime: a .dvk document written in one opens in another, and runs there, as long as the other has the nodes it uses. What differs is what each lets you do. This page sets them side by side by what you can do in each - writing programs, the nodes a program can use, building and sharing programs, the tools beside the editor, and help - and leaves out how any of it is made.

At a glance

For In one sentence
Divooka Explore learning, experimenting and everyday tasks One document at a time, every package but Machine Learning built in, nothing to set up, and a shelf of examples.
Divooka Explore Demo trying Divooka on procedural terrain Divooka Explore with only the procedural-terrain packages and two dozen examples.
Divooka Compute professional work and application development Many documents over a workspace, documents that reference packages and each other, two ways to run, a terminal, plugins, and programs you can publish.
Divooka Engine people building their own distributions Divooka Compute's editor with only the essential nodes: everything else comes from what a document references and from plugins.
Divooka Player running programs somebody shared with you No editor: drop a program on it, see what it is, and run it; free to pass on.

Divooka Compute comes in two tiers. Standard is the one a person installs. Minimal is a smaller build for development: the whole editor and its tools, with only the essential packages and no examples. A company's Divooka Compute can also come as a corporate edition, installed from an installer made for that company, which asks for an access key once per computer and checks its licence at every start.

Writing programs

Explore Explore Demo Compute Engine Player
Documents open at once one one many, in tabs, over a workspace of folders many, as in Compute -
Graph kinds you can create Flows, Function, Events, Routine, Components and Type; a document holding any other kind opens, edits and runs as Explore every kind every kind -
JSON documents (.dvj) opened as their text as Explore opened, edited and saved as documents as Compute run
Text and code files edited in the document's place, plain as Explore edited in tabs of their own, coloured as Compute -
Pictures, PDF, EPUB, Word and PowerPoint files viewed in the document's place as Explore viewed in tabs of their own as Compute -
Archives (zip, 7z, app bundles) listed, opened and extracted as Explore also added to, removed from, renamed in and saved as Compute an app bundle runs
Running interpreted, with the debugger: breakpoints, stepping, the call stack and locals as Explore interpreted with the debugger, or compiled; in the editor or in a process of its own interpreted with the debugger, or compiled runs a program, and stops it
Themes Dark Dark several built in, and theme files you add or customize Compute's its own light theme

What a program can use

Explore Explore Demo Compute Engine Player
Nodes built in every package but Machine Learning Standard Library, Platform, Graph Editor Essentials, Event Applications, State Machines, Procedural Generation, Numerics and Image Processing Minimal: the essentials. Standard: every package, Machine Learning included the essentials alone: the language, arithmetic and logic, text, the console and the asset library, Graph Editor Essentials, Event Applications and State Machines every package Compute Standard has but Machine Learning
GPU kernels - - Standard - yes
A document's references: NuGet packages, DLLs, C# files and other documents left in the document and not loaded as Explore added, removed and loaded as Compute loaded, so a program that brings its own nodes runs
Editor plugins none none a Plugins folder beside the program and your own as Compute none
Python scripts and modules as nodes - - yes; Standard also carries numpy and pandas - -
Running C#, Lua and Python scripts - - yes - -

A document written in Explore declares no packages, and reads in Compute against what that Compute ships; one written in Compute that uses a package Explore does not have, or a reference, shows those nodes as missing in Explore.

Building and sharing programs

Explore Explore Demo Compute Engine Player
Publish a document as a program of its own, for Windows or Linux, optionally as native code - - yes: the tools it builds with come with Compute - -
Methodox Action Maker: programs written as rows yes - Standard - -
Methodox App Maker: apps made by drawing their window - - Standard - -
Run a shared program without an editor - - - - yes

Tools beside the editor

Explore Explore Demo Compute Engine Player
A terminal with C#, Python, Lua and Easy Shell prompts - - yes - -
stew, the command-line runner - - yes - -
A server AI assistants write documents through, and Divooka Central's command line - - Standard - -
TranslationTool, for translating the distribution - - Standard - -
Divooka Golem, the mascot yes - Standard - -

Help, examples and languages

Explore Explore Demo Compute Engine Player
Examples the Explore pack Basics and Procedural Terrains, 24 documents Standard: the Explore and Compute packs none none
The built-in Methodox Wiki, offline in the help menu, and as Methodox Wiki beside the program as Explore as Explore online online
Languages English, 中文 and 繁體中文 as Explore as Explore as Explore as Explore, starting in the computer's own

Divooka Player

Divooka Player is for the person a program is shared with. Dropped on its window, or opened from its file, a program opens on its page: what it says about itself, how large and complex it is, what runs it, and what can be set before it runs. A program with nothing to set, one given its inputs on the command line, and a desktop application - which runs with no Player window at all, as a program of its own would - run at once. A program's inputs are its own command-line options: DivookaPlayer "Tally.dvk" --Name Ada --Count 3, and DivookaPlayer "Tally.dvk" --help lists them. It has an installer, which puts it in the Start menu and opens .dvk, .dvj and .dvb files with it where no other program opens them, and it may be passed on freely, whole.

How large each is

About 2.5 GB for Divooka Compute Standard, which carries the tools Publish builds with and a browser engine for previews; about 770 MB for Divooka Explore; about 520 MB for the Explore Demo; about 630 MB for Divooka Player; about 310 MB for Divooka Engine.

See also