feat(studio): ship JavaFX 2 Play and delegate integration tooling
Launch the JavaFX 2 project shell on Java 25 with an interactive viewport, managed Play lifecycle and project mutation guards. Preserve headless/MCP and save compatibility, and qualify exact runtime executable bundles. Separate unit JaCoCo gates from opt-in integration suites and use the internal Pong fixture for the headless visual pilot. Move maintenance and native conformance tools into tooling; retain the VS Code extension and update current navigation links. Validation: tooling make verify passed, including 1064 Studio unit tests, JaCoCo thresholds and 22 headless integration tests.
This commit is contained in:
@@ -1,18 +1,30 @@
|
||||
# JavaFX 2 Foundation Specification
|
||||
|
||||
Status: Implemented foundation. Owner: `studio`.
|
||||
Status: Implemented foundation and default product frontend. Owner: `studio`.
|
||||
|
||||
## Scope and precedence
|
||||
|
||||
This document governs `prometeu-studio-ui-javafx-2`, an independent replacement frontend foundation. It defines the minimal shell, presentation components, themes, localization and typography. It does not redefine Studio API/Core, MCP, asset banks or runtime contracts.
|
||||
|
||||
The existing frontend and its launcher remain available. Specifications 1–4 continue to describe that frontend's current shell/components/workspaces; they are not a visual or architectural template for JavaFX 2. Later capabilities must extend the new foundation through their own explicit contracts.
|
||||
The normal application now uses this frontend, with project/Play integration owned
|
||||
by the [Integrated Play Specification](14.%20Integrated%20Play%20Specification.md).
|
||||
The previous module is retained for consultation and adapter qualification.
|
||||
Specifications 1–4 describe its shell/components/workspaces; they are not a visual
|
||||
template for JavaFX 2. Later capabilities must extend the foundation through their
|
||||
own explicit contracts.
|
||||
|
||||
## Shell
|
||||
|
||||
The default launch MUST show a native-decorated window with Studio identity, theme/language selectors and an empty central working area. Minimum outer window size is 680×480; the initial scene is 1200×800. Toolbar content MUST wrap/reflow instead of requiring horizontal scrolling at the supported minimum width.
|
||||
The standalone foundation launch MUST show a native-decorated window with Studio
|
||||
identity, presentation selectors and an empty working area. The product mounts its
|
||||
chooser/Play view there. Minimum outer size is 680×480; the foundation initial scene
|
||||
is 1200×800, and the integrated product starts at 1200×850. Toolbar content MUST
|
||||
wrap/reflow instead of requiring horizontal scrolling at the minimum width.
|
||||
|
||||
The shell MUST NOT initialize a game project, backend service graph, runtime or agent. It MUST NOT contain fictitious editor tabs, operations or domain panels. The component gallery is a separate developer launch, not a product workspace.
|
||||
The shell component and standalone demonstrations MUST NOT initialize a project,
|
||||
backend graph, runtime or agent. Product services are injected into a separate
|
||||
coordinator by the app. There MUST be no fictitious editor tabs or domain panels.
|
||||
The component gallery is a separate developer launch, not a product workspace.
|
||||
|
||||
## Presentation ownership
|
||||
|
||||
@@ -46,4 +58,8 @@ The foundation MUST have display-free tests of its own locale/preferences/resour
|
||||
|
||||
Initial qualification is on available macOS. Windows/Linux, assistive-technology walkthroughs and native IME composition require their own evidence. Logical scene snapshots MUST NOT be presented as proof of physical pixel alignment at every HiDPI scale.
|
||||
|
||||
Project navigation, document host, free docking, ACP, asset workflows, code/LSP editor, scene/entity authoring, pixels/audio editing and Shipper are outside this foundation contract. Backend integrations MUST use existing application services when those features are introduced; domain logic MUST NOT be duplicated here.
|
||||
Project navigation and integrated Play are specified separately by specification
|
||||
14. Document host, free docking, ACP, asset workflows, code/LSP editor, scene/entity
|
||||
authoring, pixels/audio editing and shipping remain outside this foundation
|
||||
contract. Backend integrations MUST use existing application services; domain logic
|
||||
MUST NOT be duplicated here.
|
||||
|
||||
Reference in New Issue
Block a user