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

Move app UI workflows into UI target

Browse Source
This commit is contained in:
omigamedev
2026-06-02 21:48:17 +02:00
parent 3a1ca7a8e6
commit b84dfc049d
3 changed files with 31 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/modernization/roadmap.md
View File

@@ -148,10 +148,11 @@ option targets exist. The Windows desktop app builds through CMake as
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. The first `pp_panopainter_ui` target now owns a
small app-specific modal/help UI group (`NodeAbout`, `NodeChangelog`,
`NodeMessageBox`, `NodeMetadata`, and `NodeUserManual`) outside
`pp_legacy_app`. Android arm64 now configures and builds headless
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.