Combine canvas and control panel workspace

[codexbountylab]

Summary

• combine the Processing canvas and the existing control panel into one main Quantum Brush workspace window
• keep the effect/hardware controls on the left and the drawable canvas on the right using a resizable split pane
• resize and keep the unified window on screen when the canvas size changes after loading images
• preserve the existing hardware token cleanup on close

Closes #48.

Validation

• Compiled locally with OpenJDK 21:
  javac -cp "lib\core-4.4.1.jar" -d <temporary-output-dir> src\*.java
• git diff --check

AI disclosure

I used an AI coding assistant to help inspect the existing Swing/Processing UI structure and draft this change. I reviewed the resulting code and validated it locally with the compilation command above.

[codexbountylab]

Hi @artreadcode, thanks for taking a look. I’ve attached the requested screenshot, working GIF, and a complete Java 17+ test jar packaged as a zip because GitHub comments do not allow direct jar uploads.

The jar includes the effect files and extracts them on startup, so it can be run as a standalone test build. The GIF shows the unified workspace with the effect controls and canvas in the same window.

QuantumBrush-unified-workspace-java17-complete.zip

[codexbountylab]

@artreadcode thank you for the update.

I prepared a combined test build that includes both fixes:

• Combine canvas and control panel workspace #64 / Combine the Control Panel with the Canvas window #48: unified workspace, updated canvas sizing, and centered empty-canvas placeholder
• Add in-memory stroke transport #67 / Serialization and what's next? Improve communication between different language stack #47: in-memory Java/Python stroke transport without per-stroke input/output PNG files

I tested the combined build locally. After creating/running/applying strokes, the file-write monitor shows:

*_input.png : 0
*_output.png: 0

The project still writes the normal project files (original.png, current.png, and stroke instruction JSON), but it no longer writes per-stroke *_input.png or *_output.png files.

QuantumBrush-combined-test.zip

[artreadcode]

@codexbountylab Hello, thank you for your email. For some reason, when I run the algorithm, it shows multiple errors, I assume it's because of changed codes in the Python side. Can you provide the .zip file of the changed codes on the Python side so that I can test it out the deployed .jar well? Best regards, Astryd

[artreadcode]

Here are the bugs that I said:

[codexbountylab]

@artreadcode thanks for the screenshots. I found that the packaged build can still depend on the launch directory when starting the Python effect process, so running the jar directly can break the Python side and lead to the broken-pipe error.

I’m fixing that now so the jar resolves the bundled effect/ folder from the application directory instead of depending on the current working directory. I’ll upload a clean full zip again once I verify it locally.

[artreadcode]

@codexbountylab That is true. There are multiple broken pipelines that are now confirmed, so I hope it could be resolved.