📄️ Overview
This documentation is a reference documentation for developers creating extensions for Picteus. Picteus extensions enable you to extend the application's capabilities with custom image processing algorithms, automated tagging and feature extraction, interactive user interfaces, external tool integrations, and custom workflow commands.
📄️ Manifest
Every extension must include a manifest.json file in its root directory. This manifest acts as the formal contract between the application and the extension, defining metadata, required runtimes, execution instructions, event subscriptions, registered commands, settings schemas, and user interface elements.
📄️ Class
Every Picteus extension must define an implementation class that inherits from the PicteusExtension base class provided by the official SDK. This class acts as the core entry point of your extension, overloading lifecycle hooks, subscribing to domain events, handling UI commands, and coordinating interactions with the Picteus application.
📄️ API
Picteus extension SDKs embed the entirety of the back-end REST web services API, completely generated from OpenAPI specifications. Extensions can interact with any back-end resource — images, repositories, collections, tags, features, secrets — without requiring manual HTTP request configuration.
🗃️ ViewKit
1 item
🗃️ Intents
1 item
📄️ Manual
The MANUAL.md file is an optional Markdown document located at the root of an extension directory. It acts as the user manual and contextual in-app documentation for the extension.