Expand description
Plugin discovery, lifecycle management, and permission-aware execution.
gestura-core-plugins provides the workspace plugin domain: manifest-backed
discovery, lifecycle state management, plugin permission metadata, and a
shared plugin manager that can be consumed by higher-level runtime code.
§Main concepts
PluginMetadata: manifest-level identity, versioning, and descriptive dataPluginDependency: declared plugin dependency edgesPluginPermission: requested capability set for the pluginPluginState: lifecycle state such as loaded, running, or failedPluginManager: discovery, load/unload, start/stop, command execution, and event broadcast coordination
§Architecture role
This crate owns the plugin domain model and manager implementation. It does not try to turn plugins into a separate presentation or orchestration layer; instead, it provides a core-owned substrate that other application surfaces can use consistently.
§Stable import paths
Most application code should import through gestura_core::plugin_system::*.
Structs§
- Plugin
- Plugin instance.
- Plugin
Dependency - Plugin dependency.
- Plugin
Manager - Plugin manager.
- Plugin
Metadata - Plugin metadata.
Enums§
- Plugin
Permission - Plugin permissions.
- Plugin
State - Plugin state.
Traits§
- Plugin
Api - Plugin API interface.
Functions§
- get_
plugin_ manager - Get the global plugin manager.