FLTK VS imgui

Another dark horse is FLTK: https://www.fltk.org/. For utilities this might be your best choice, especially because static linking is supported. This is mostly a C++ solution but there are bindings to other solutions.

Fl_Flex (shameless plug!) is now officially in upstream FLTK since 1.4 for a "flexbox style" layout manager.

Go ahead and sell an FLTK product then. I'm sure you go to https://www.fltk.org/ and think those GUI's look awesome you delusional moron

FLTK

A few examples: Dear ImGui, SFML, FLTK. Probably even Tk could be used.

FLTK (Fast Light Toolkit) is a lightweight, cross-platform supported toolkit for building GUIs. FLTK is supported on Windows, macOS, and UNIX systems and was originally built for C++. If you use the FLTK toolkit to create a GUI application, the application looks the same on all supported operating systems.

There are a lot of options and they're not that hard to find... Qt, wxWidgets, FLTK, IUP come immediately to mind.

FLTK. It's a cross-platform C++ GUI toolkit for UNIX®/Linux® (X11), Microsoft® Windows®, and MacOS® X.

Cool project! Graphics programming is _hard_ and anything to make it easier is welcome.

Maybe a dumb question, but why not Imgui (https://github.com/ocornut/imgui). "It's way too big and complex" is a completely reasonable answer, but I found it fantastic for debug menus, and there are a few applications that have used it as their _main_ GUI (Ship of Harkinian as an example).

The most well known immediate mode GUI framework, which egui is also inspired by, is Dear imgui. The egui repository also has a section on the trade offs when it comes to immediate mode GUIs, which I would definitely recommend you check out.

> "Minimize state synchronization."

> void UpdateUI()

Minimize state synchronization by effectively synchronizing state on each screen refresh?

> "Minimize state storage on user side."

> Immediate mode is a style of API where important state is kept in user code

Then reduce state stored in user code by storing "important state" in user code?

> "Minimize setup and maintenance."

I don't find the example convincing. It seems like any more complexity beyond this toy example puts you right back where you started. Building components by hand is stone age ideology regardless of how you push state.

https://github.com/ocornut/imgui/blob/master/examples/exampl...

> "Easy to use to create dynamic UI which are the reflection of a dynamic data set."

Which is great for a video game.

A few JavaFX issues I've encountered while writing KeenWrite[1], my FOSS text editor based heavily on JavaFX:

* Building installer-free cross-platform binaries on a local Linux build machine requires an external packager[2].

* Good luck building an installer-free binary for CPU architectures that differ from the compiler's machine.

* Creating a Windows version will cost $ (to sign).

* Creating a macOS version will cost $ (to sign).

* WebView is a bloated beast that bundles JavaScript and exposes no API to set scrollbar positions.

* FlyingSaucer[3] is a lightweight alternative to WebView, but requires a SwingNode.

* SwingNodes are blurry on Windows.

* SwingNodes issue GDK-3 warnings on Linux.

* Menu latching messes up cross-platform (Alt+Tab is a wrench).

* Modular applications are a pain. Migration has been poorly communicated, poorly documented, and poorly supported.

* RichTextFX has no way of changing the caret style in insert mode.

* PreferencesFX, and likely other FX libraries, has security issues.

* For MDI with dockable panes, you'll need tiwulfx-dock[4].

Java problems:

* Write-once, run anywhere is no longer true.

* Apache Batik for rendering SVG images is buggy, EchoSVG[5] is better.

* Rendering math as SVG is hard[6].

* Cross-platform user data directory that complies with XDG, Windows, and macOS will take effort.

* Reliably locating executable programs cross-platform is a chore.

Depending on your requirements, C++ and imgui may be a better choice.[7]

[1]: https://gitlab.com/DaveJarvis/KeenWrite

[2]: https://github.com/Reisz/warp/

[3]: https://github.com/flyingsaucerproject/flyingsaucer

[4]: https://github.com/panemu/tiwulfx-dock

[5]: https://github.com/css4j/echosvg

[6]: https://gitlab.com/DaveJarvis/KeenType

[7]: https://github.com/ocornut/imgui/issues/4400#issuecomment-89...

> I switched from C++ to C about 7 years ago and never looked back

I'm definitely considering the same, and you're right - it's not C++ itself that appeals to me at all, it's the libraries. I'm not sure what C libraries I'd use for collections (instead of the STL and Abseil [0]), or in lieu of CLI11 [1] or Dear ImGui [2].

[0] https://abseil.io/about/design/swisstables

[1] https://github.com/CLIUtils/CLI11

[2] https://github.com/ocornut/imgui

This discussion around adding shadows to window boarders in imgui is also interesting: https://github.com/ocornut/imgui/issues/1329

I think that world still exists. We're on HN, so there's always going to be a business/startup bias in what we talk about and share here. And doubly so if someone develops a product as open source with a commercial offering to support it from the get go.

Off the top of my head, Imgui[0] is an example of an open source project, widely used, developed by a small group with a main contributor. AssetCooker [1] is a project that I discovered recently which is clearly a passion project from a single developer who shared it with the world. CNCF [2] is an odd one, but in my mind it's a 21st century Apache foundation - they have a bunch of core projects which are complete open source projects, used widely in production and sustained through different models.

I think imgui (of the bunch) is probably closest to the GCC-of-the-early-90's idea.

[0] https://github.com/ocornut/imgui

[1] https://github.com/jlaumon/AssetCooker

[2] https://www.cncf.io/projects/

It's even worse.

> Those were only a few options that I considered. After a very long time trying out all sorts of different libraries and at one point even writing my own MFC styles, I figured out that for simple apps there is simply nothing better suited than Dear ImGui.

They decided to go with the option that deviates the most from the standard Windows UI because there are no native controls at all and it's a nightmare for accessibility (see https://github.com/ocornut/imgui/issues/4122). I use it for prototyping privately, but I'd never make anything I want to release into the world with it.