Re: [fltk.general] FLTK vs NTK - Forums - Fast Light Toolkit (FLTK)

On Mon, 19 Jul 2021, 08:22 janezz55 wrote:

this is why Qt has it's own built-in "GLEW".

Sure, but it's a "horses for courses" sort of choice and doesn't sit well with fltk's light weight ethos.
Larger toolkits can make that accomodation more readily. Which is why a variety of different toolkits with different capacities is such a useful feature of development now, in many ways.
Bundling nanosvg and cairo support with fltk was a heavier choice than bundling some glue code would be, IMO.

Nanosvg is pretty compact, essentially just a header file, and a fairly small one at that, so if you don't use the SVG it doesn't bulk up the code so much.

GLEW can also be reduced to just a header, pretty much, but it's a lot bigger and more complex and ideally needs to be matched to the host platform which can make it trickier to decide what to bundle with a cross platform lib like fltk.

The Cairo hooks are trickier for me as I don't really like how they work, or really see the point of them since it's trivial to get a Cairo context in a fltk window. Of course the Cairo stuff is not included by default anyway, unless you explicitly enable it during configuration, so again has little affect for most users.

But really, if you try the samples in the "test" folder you'll quickly see the one I mean. Just give them a try.
I'll check it out.

They're all just small samples to exercise the various functional aspects, but worth a look.

Both the "test" and "examples" folders have some interesting bits.
--
Ian
From my Fairphone FP3