omar/panopainter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move app orchestration into app target

Browse Source
This commit is contained in:
omigamedev
2026-06-02 21:50:07 +02:00
parent b84dfc049d
commit 6fda4d4a90
3 changed files with 20 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/modernization/roadmap.md
View File

@@ -147,12 +147,13 @@ option targets exist. The Windows desktop app builds through CMake as
`PanoPainter` is only the executable/resource wrapper; Windows and vendor link
dependencies now belong to the platform shell target, and Windows runtime
payload deployment lives behind `cmake/PanoPainterRuntime.cmake`.
`panopainter_app` is now a real static target that owns app version metadata
and version-header generation. `pp_panopainter_ui` now owns app-specific modal,
dialog, panel, canvas, viewport, color-picker, stroke-preview, and tool UI
workflow nodes outside `pp_legacy_app`; base `Node` controls and layout
plumbing remain in the legacy target until the UI core/app UI boundary is
tightened. Android arm64 now configures and builds headless
`panopainter_app` is now a real static target that owns app orchestration
sources, app version metadata, and version-header generation.
`pp_panopainter_ui` now owns app-specific modal, dialog, panel, canvas,
viewport, color-picker, stroke-preview, and tool UI workflow nodes outside
`pp_legacy_app`; base `Node` controls and layout plumbing remain in the legacy
target until the UI core/app UI boundary is tightened. Android arm64 now
configures and builds headless
foundation/tool targets through the root CMake/NDK path. Non-Windows platform
app/package files remain during Phase 6 alignment.