Overview

JadeGit supports an experimental mode that enables functionality not yet considered stable.

Experimental features are intended for evaluation and iteration. Behaviour and interfaces may change as the underlying model evolves.

Experimental mode is an all-or-nothing setting that activates all experimental features in scope of where it has been enabled. There is no per-feature toggle.

Command-Line

Experimental mode can be enabled at the database level using the JadeGit console:

jadegit -p <system> -i <ini> experimental --enable

To disable:

jadegit -p <system> -i <ini> experimental --disable

When enabled at the database level, the experimental state is stored in the registry. This allows independent configuration for different environments (for example, development and test databases) and lays the groundwork for future deployment-related experimental behaviour.

Configuration

Experimental mode can also be enabled via the Jade initialization file:

[JadeGit]
Experimental=true

This setting defaults to the database-level registry value but overrides it when present. It enables experimental functionality in the user interface and may be per user in future when thin-clients are supported.

User Interface

When opening the context menu at the top of the JadeGit Changes explorer while holding Ctrl, a hidden menu option appears. This allows the experimental mode to be toggled for the user interface at runtime.