aboutsummaryrefslogtreecommitdiffstats
path: root/lib/openjfx/api-ms-win-crt-utility-l1-1-0.dll
diff options
context:
space:
mode:
authorKostya <mail@sartin.in>2026-10-11 19:28:04 +0300
committerKostya <mail@sartin.in>2026-10-11 19:28:30 +0300
commit3a734b84705ccb8174e9cf24b74d7a3c3b2c1beb (patch)
tree80408f2f1e6af973b1f61288c87a89b4ee8e96d3 /lib/openjfx/api-ms-win-crt-utility-l1-1-0.dll
parentdc616e0f340f28b320253bf9a70778a07b885ffd (diff)
downloadguess-market-3a734b84705ccb8174e9cf24b74d7a3c3b2c1beb.tar.gz
guess-market-3a734b84705ccb8174e9cf24b74d7a3c3b2c1beb.tar.xz
guess-market-3a734b84705ccb8174e9cf24b74d7a3c3b2c1beb.zip
ui-fx: move the JavaFX UI into a module that sees only the api
Exercise 3 asks for a new desktop client that reuses the Exercise 2 screens, and the course asks that clients depend on the DTO contract, never on the engine. ui-desktop mixed both: its views and controllers only talk to the api interfaces, but AppView and AppState each had a convenience constructor that built a ServiceEngine, which tied every UI class to the service module. Move the screens, controllers, components, FXML, skins and fonts into a new ui-fx module that depends on api alone. Packages are unchanged, so FXML controller names and resource paths keep working as they are. ui-desktop keeps only the Exercise 2 app: Launcher, App, which now builds the ServiceEngine and passes its contexts in, and ServiceEngine itself. The Exercise 3 client can then reuse ui-fx with remote contexts and never put the engine on its classpath. The build proves the split: ui-fx compiles with nothing but api visible. Tests move with the code they cover. AppStateTest drives the real engine, so it stays in ui-desktop.
Diffstat (limited to 'lib/openjfx/api-ms-win-crt-utility-l1-1-0.dll')
0 files changed, 0 insertions, 0 deletions