FLTK 1.4 Released With Wayland & HiDPI Display Support

[phoronix]

Phoronix: FLTK 1.4 Released With Wayland & HiDPI Display Support

FLTK 1.4 is out as the newest version of the Fast Light Toolkit that has been around since the late 90's...

https://www.phoronix.com/news/FLTK-1.4-Released

[uid313]

Yuck, this one is ugly! Use GTK or Qt instead!

What's next, they're bringing Motif to Wayland?

[mazumoto]

Now that's what I call a Scrollbar and a Button.
Looks usable.

[mobadboy]

( ) Beautiful appearance
( ) Reasonable UX
( ) Kept up with remotely modern design philosophies
(X) Extremely nostalgic
(X) Assisting in the deprecation of Xorg in most situations

they know what matters

[cutterjohn]

holy crap! FLTK is still around... nice to see in a way... I guess...

[primary]

that website.. my god I love it.

[Raka555]

Yuck, this one is ugly! Use GTK or Qt instead!

What's next, they're bringing Motif to Wayland?

The FL in FLTK stands for fast and light, things GTK and Qt are not ...
But it remains to be seen how much of the "FL" it retains.

Was going to say you should see Motif if you think this is ugly, but looks like you know

[mifritscher]

I like the simple yet functional style. Esp. normal scrollbars (scrollbar do carry lot of information, e.g. "how much stuff and how much in relation to the screen size" - I really hate the tiny or even autohidding versions which spreads more and more) and Buttons which looks like - buttons! On more and more Toolkits you can not tell whether you can click on text or not.

[topolinik]

The FL in FLTK stands for fast and light, things GTK and Qt are not ...
But it remains to be seen how much of the "FL" it retains.

Being a whole graphic toolkit packed into less than ten megabytes, chances are it still performs lean and reactive.

[eltomito]

Yuck, this one is ugly! Use GTK or Qt instead!

I use it for an industrial app that runs on Windows and Linux and it's so much less hassle and B.S. than GTK or Qt!
I worked on a GTK app some time ago and once it took me two days to figure out how to write a dynamic pointer cast to make a widget work.
Also, GTK makes you write everything in GTK. You have to derive pretty much all your types from their GObject, use their storage structures in order to be able to display the data, etc. so if you eventually want to move away from GTK, it means rewriting the whole program.
Qt is even worse in this way. You actually have to learn a whole new language (called Q) to even use it. And the bloat goes beyond any measure.
So unless I'm making an app that has to appeal to teenagers hooked on Anime, I'd go for FLTK instead of GTK or Qt any day.