2.6 KiB
2.6 KiB
Scene Integration Specs
This directory contains boundaries with host applications, external UI systems, threading, custom visuals, and display integration.
Use these files when scene behavior crosses into application-owned state, UI frameworks, background threads, high-DPI windows, or custom user-provided visual families.
Files
- EXTERNAL_UI.md: boundary with UI frameworks such as ImGui.
- THREAD_SAFETY.md: threading model and async data handoff.
- HIGH_DPI.md: logical pixels, device pixel ratio, and DPI changes.
- DPI_SCALE_IMPLEMENTATION_PLAN.md: implementation roadmap for high-DPI consistency and dynamic user scale.
- HIDPI_LIVE_WINDOW_IMPLEMENTATION.md: live GLFW high-DPI sizing, input normalization, and text-anchor implementation plan.
- OPTIONAL_PROVIDERS.md: optional dependency, bridge, recipe, custom visual, and technique extension boundaries.
- CUSTOM_VISUALS.md: registration and integration of user-defined visuals.
- HOSTED_BACKENDS.md: Qt, Python console, IPython, Jupyter, SDL, Tk, and other host-owned event-loop integrations.
- CUPY_CUDA_INTEROP.md: zero-copy CUDA/CuPy memory sharing design for real-time Datoviz visualization.
- NVDEC_VIDEO_SOURCE_PLAN.md: future low-level video source and NVIDIA hardware-decode plan for image/sampled-field workflows.
- TIMED_MEDIA_SYNC.md: future synchronized video, audio, events, and signal timing model for scientific playback and analysis.
- ENTRY_POINTS.md: low-level and hybrid public integration lanes for canvas, vklite, DRP2, scene export, and full scene/app usage.
- WEBGPU_WASM.md: experimental browser WebGPU and WASM scene integration contract.
- WASM_WEBGPU_PARITY_PLAN.md: implementation plan for broad native Vulkan and WASM/WebGPU scene parity.
- GSP_TEXTURE2D_MESH_PLAN.md: Datoviz-side plan for generic field-slot sampling needed by GSP strict Texture2D meshes.
- future: Android, iOS, and touch pressure notes.
- napari: informative napari adapter guidance and historical PoC notes.