C++ developer API

A native plugin links ew::core + ew::app, so the whole public surface of both libraries is the developer API — a stable, documented contract you can build on. Register a plugin (a colour theme, an AI command, a dockable panel, or a menu command), then read and edit the open project through the same model and engines the app itself uses.

Write your first plugin

A walkthrough that builds a dockable panel reading the codex and the relationship graph.

Building & installing

ABI versioning, qt_add_plugin, and where the app looks for plugins.

Start here

Plugin

The plugin interface every plugin implements.

PluginContext

Register a plugin's themes, commands, and panels.

PluginAppContext

The live handle a panel/command uses to read and edit the project.

Project

The open project: read and traverse the whole model.

Entity

A codex entity — fields, aliases, gallery, state over time.

RelationshipGraph

Build and lay out the entity relationship graph.

Browse the API

Every public type and function, grouped by module. Or use the search box.

ew::core 172 headers

The UI-agnostic model: content objects, the project, commands, value types.

ew::app 223 headers

The engines over the model: queries, analytics, exports, the graph, the host.