Expand description
PLAYA - Image sequence player library
Re-exports all modules for use by binary targets.
Re-exports§
pub use runner::run_app;pub use core::cache_man::CacheManager;pub use core::event_bus::downcast_event;pub use core::event_bus::BoxedEvent;pub use core::event_bus::CompEventEmitter;pub use core::event_bus::EventBus;pub use core::event_bus::EventEmitter;pub use core::global_cache::GlobalFrameCache;pub use entities::CacheStrategy;pub use core::player::Player;pub use entities::Attrs;pub use entities::AttrValue;pub use entities::Comp;pub use entities::Frame;pub use entities::Project;
Modules§
- app
- Application module - PlayaApp and related functionality.
- cli
- config
- Application configuration: paths, defaults, and theme colors.
- core
- Core engine modules - cache, events, player, workers
- dialogs
- Dialogs - modal and non-modal dialog windows
- entities
- Entities module - core types with separation of business logic and GUI.
Data flow: UI/EventBus drives mutations on
Project/Comp/Attrs; loaders and compositor produceFramedata that UI/encoding consume. - help
- Per-window help system with two-column layout.
- main_
events - Application event handling - extracted from main.rs for clarity.
- runner
- Application runner - entry point for both CLI and Python bindings.
- server
- REST API server for remote control of the player.
- shell
- Shared shell module for standalone binary targets.
- ui
- Top-level egui wiring for the Playa UI.
- utils
- Utility functions and constants
- widgets
- UI Widgets - modular, reusable UI components