Source code: https://github.com/uyjulian/fltkbasiliskgui
To compile, use fluid to generate C++ code, and compile the source code in C++11 mode.

It actually works this time!


This should be functionally similar to the GTK version of the GUI. Some features are not implemented, like disk image creation, zapping PRAM, or launching Basilisk II.

I'm writing a nice build system right now. For now, you can download the debug binary for macOS:
https://transfer.sh/6UVlq/fltkbasiliskgui_bin.zip

EDIT: Here is a Application Bundle that contains its own copy of FLTK, so should work without having FLTK installed via homebrew:
https://transfer.sh/SOqBE/fltkbasiliskgui.app.zip
Please report any problems or issues that may arise!

Nice stuffs. Are you going to send a PR to upstream once it is ready?

_________________
There is an App for that!
https://github.com/rickyzhang82

I'm not planning to send a PR to upstream right now because it uses fluid, which might be confusing to whoever wants to work on the GUI. Also, this program uses its own code for reading/writing the config file instead of BasiliskII's code like what the GTK GUI is doing.

How does Fluid compare to a simple language like TCL? You've already got the TK widgets, so it seems to me moving over from Fluid to TCL would be rather trivial for the back end... and then you've got a tool chain that's standard on everything but Windows and is very lightweight.

Although it might be interesting to modify the GTK code inside BII to just run handlers for the file operations so you could use whatever you want on the front end (like UME does)....