←back to thread

FLTK 1.4 Released

(www.fltk.org)
113 points mappu | 2 comments | 19 Nov 24 20:17 UTC | HN request time: 0.467s | source
Show context
chrsw ◴[20 Nov 24 06:47 UTC] No.42191358[source]▶
The FLTK use case seems to overlap heavily with wxWidgets. Are there reasons to choose one over the other?
replies(1): >>42191566 #
1. beagle3 ◴[20 Nov 24 07:33 UTC] No.42191566[source]▶
WxWidgets uses native widgets, for better (e.g. automation, screen readers) and for worse (weird platform differences, flickering, lots of “common ground” limitations).

FLTK draws the controls on its own - for the better (incredibly fast, consistent across platforms, flicker free since 1998, super easy to implement new widgets) and for the worse (bad support for complex text layout in Asian and bidi languages, no support for accessibility)

I would say it’s the wrong tool for a mass-market product or if you need non European language support.

It’s the perfect tool for internal projects that only require European/English languages.

In between those, depend on the details.

replies(1): >>42193116 #
2. chrsw ◴[20 Nov 24 12:03 UTC] No.42193116[source]▶
Great explanation. Thanks.