andras/schmelczer-dev
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

Update content & design (#75)
All checks were successful
Deploy to Pages / build (push) Successful in 2m58s
Details

Browse source 
Reviewed-on: https://home.schmelczer.dev/git/git/andras/schmelczer-dev/pulls/75
This commit is contained in:
Andras Schmelczer 2026-05-28 16:20:12 +01:00
parent 0be50b6c24
commit b554e92e9f
83 changed files with 2995 additions and 723 deletions
Download patch file Download diff file Expand all files Collapse all files

12
src/content/posts/graph-editor-javafx-simulation-input.md
View file

@ -1,6 +1,6 @@
---
title: A JavaFX Graph Editor for Simulation Input
description: A small JavaFX editor for creating and uploading graph input for the cooling system simulator.
title: A JavaFX Editor for the Cooling Simulator
description: The companion editor for the cooling-system sim. Drag-and-drop graph layout, JSON export, upload-to-backend. Small tool, mattered more than I expected.
date: 2026-04-25
projectPeriod: 'October-November 2018'
thumbnail:
@ -9,13 +9,11 @@ thumbnail:
tags: ['simulation', 'tools']
role: Editor author
stack: ['JavaFX', 'JSON', 'REST API']
outcome: An editor for building input graphs and sending them to the simulation backend
outcome: A drag-and-drop graph editor that let non-developers feed the simulator
audience: technical
links: []
---
This was a small editor for building input graphs for the cooling system simulator.
Non-technical event organisers needed to rewire a cooling plant in real time without me hovering. That was the brief, and it ruled out every interface I'd have enjoyed writing. The [cooling system sim](/articles/nuclear-cooling-simulation/) was only as useful as the tool that fed it, so in late 2018 I built a JavaFX desktop editor: lay out the plant as a graph, edit each element's parameters in a side panel, export JSON, or upload straight to the backend.
Nodes could be moved with drag-and-drop gestures. Element parameters were edited on the right panel.
The UI was built with JavaFX. The output could be exported as JSON or uploaded directly to the simulation backend.
Small tool, and the whole event hinged on it. If I built it again I'd skip JavaFX and put the editor in the browser next to the monitoring clients. One install fewer for everyone, and one fewer reason for someone to call me over.