Files
prometeu-studio/docs/specs/studio/3. Studio Components Module Specification.md
bquarkz a0a5050d5e
Intrepid/Prometeu/Studio/pipeline/pr-master Build started...
JaCoCo Coverage #### Project Overview No changes detected, that affect the code coverage. * Line Coverage: 64.01% (20482/31999) * Branch Coverage: 54.22% (8240/15196) * Lines of Code: 31999 * Cyclomatic Complexity: 13164 #### Quality Gates Summary Output truncated.
Test / Build skipped: 15, passed: 715
Intrepid/Prometeu/Studio/pipeline/head This commit looks good
complete Studio core and JavaFX boundary migration
2026-09-25 11:28:18 +01:00

3.2 KiB

Studio JavaFX Components Boundary Specification

Status

Active

Applies To

  • prometeu-studio-ui-javafx
  • shared Studio controls and workspace-framework primitives
  • JavaFX controls actively used by the Studio

Purpose

Define the visual component boundary inside the JavaFX adapter without creating a second application or domain layer.

Authority and Precedence

This specification is subordinate to 9. Studio Core and Adapter Architecture Specification.md.

Core Rules

  1. Reusable Studio visual controls belong to prometeu-studio-ui-javafx.
  2. The JavaFX adapter may organize reusable controls by shell, forms, banks, lifecycle, navigation, feedback, and inspection roles.
  3. A control is admitted when it has an immediate Studio consumer; speculative mirroring of JavaFX is forbidden.
  4. Shared controls must preserve theme, localization, and explicit visual-state behavior.
  5. Controls that observe UI events must expose predictable attach/detach or subscribe/unsubscribe lifecycle behavior.
  6. Visual controls must depend on neutral Studio API contracts, not core or provider implementations.
  7. Domain rules, application orchestration, filesystem workflows, compiler/Packer/LSP/runtime calls, and Spring composition do not belong in the visual component layer.

JavaFX Wrapping Boundary

The Studio may use raw JavaFX for trivial local composition. A reusable control should expose the Studio-facing API actually needed instead of cloning the complete upstream JavaFX surface.

Shared controls may include:

  • shell and action controls;
  • workspace rails and hosts;
  • form sections and action bars;
  • list, tree, inspector, and dual-list surfaces;
  • activity, progress, badges, headers, and feedback controls;
  • lifecycle-managed visual primitives.

Construction and Lifecycle

Controls, rows, dialogs, and views MUST NOT be Spring singletons by default. A Spring-managed JavaFX composition factory may create them with explicit constructor dependencies.

Controls that attach event subscriptions MUST release them when detached. UI-local events may coordinate selection, navigation, editing scope, attach/detach, and presentation refresh. Request/response application behavior MUST use injected Studio API services directly.

State Boundary

Presentation-only view models, form drafts, selection state, and formatting helpers may live beside JavaFX controls when they do not determine domain outcomes.

Non-visual policies and workflows that determine asset validity, capacity, metadata, build, runtime, project, or semantic results MUST live behind prometeu-studio-api and be implemented by prometeu-studio-core or an explicit infrastructure adapter.

Non-Goals

  • creating a standalone prometeu-studio-components Gradle module;
  • wrapping the full JavaFX API;
  • storing workspace business logic in controls;
  • using Spring as a registry for each visual object;
  • defining components for a future web UI.

Exit Criteria

This specification is satisfied when reusable JavaFX controls have clear visual ownership, explicit lifecycle behavior, neutral injected dependencies, and no application or provider implementation responsibilities.