DrRacket seems to have doing the thing where they implement of a bunch of GUI stuff from scratch and miss a lot of edge cases in the process. It feels unpolished and a bit janky.
DrRacket seems to have doing the thing where they implement of a bunch of GUI stuff from scratch ...
The GUIs actually use the underlying native GUIs thanks to the dynamic FFI.
The goal is to have a cross platform GUI. Your program runs on macOS, Linux and Windows without any problems.
But if there is some gui feature, that is only available on one platform, you won't find it in the builtin gui libraries. However, you can always add platform specific functionality yourself.
Comments
DrRacket seems to have doing the thing where they implement of a bunch of GUI stuff from scratch and miss a lot of edge cases in the process. It feels unpolished and a bit janky.
The GUIs actually use the underlying native GUIs thanks to the dynamic FFI. The goal is to have a cross platform GUI. Your program runs on macOS, Linux and Windows without any problems.
But if there is some gui feature, that is only available on one platform, you won't find it in the builtin gui libraries. However, you can always add platform specific functionality yourself.
I can't attest to the implementation. I can only attest to the jank.
The Rhombus gui library provides a reactive framework for constructing graphical user interface (GUI) applications.
https://docs.racket-lang.org/rhombus-gui/index.html?fam=Rhom...
Because it builds on the Racket platform you get one of the only cross-platform uniform gui toolkits that works out of the box.