>>>>> "Kevin" == Kevin Smith <sent / qualitycode.com> writes:

please let me swap your both paragraphs in my answer first answering
you last one:

    Kevin> I personally haven't used FLTK, but am curious if anyone
    Kevin> here has. And if so, what do you think about it. If not,
    Kevin> why have you chosen one of the other options?

Thank you for asking ...

I have used some toolkits for my developement during the time. TK,
GTK+, QT and FLTK.

I had a look onto wxWindows, FOX, MFC, GraphApp to mention only some
of them.

But I still stick with FLTK whereever I can as it is mature, very
small, thought thru (designed) for memory footprint and speed. It is
easy to use and looks much nicer than e.g. GTK+, IMHO.

It is designed for statical linking, but can also be linked-in
dynamically. Applications tend to remain very small even if FLTK is
statically linked-in. Let me mention two examples; all statically
linked against FLTK, stripped and without debugging informations:

   - Its GUI builder 'fluid' containing all widgets
     linked in                      --> 294.272 bytes
   - Its demo 'checker', full functional allowing you to play
     checker against the computer   --> 109.224 bytes

Really nice stuff :-)

    Kevin> We've been actively discussing Tk, GTK, FOX, and wx. What
    Kevin> happened to FLTK? It seems very lightweight (plus), already
    Kevin> exists for ruby (plus), and supports Windows (plus). It may
    Kevin> have few widgets? (minus), and does not support Mac
    Kevin> (minus).

Agree with the lightwight and Windows plus'. Unfortunately the ruby
binding is not complete yet. The Mac support is under way (beta
already exists, IMO). And it has a lot of widgets, to answer your
question, but, perhaps, you would have take the FLEK too to get some
of them!

BTW: Due to the several mention of FOX, I have download it, and again
had a look on it to see what changed after my last trip. Not all too
much, IMO. FOX seems to be a nice, good-looking alternative. But I
still do not like the complicate way of building applications by
deriving widgets, declaring messages (enum), implementing callback
methods and announcing them via a message <-> method table.

But this is perhaps a matter of taste! I like the QT signal-slot way
or the lightwight way of FLTK using callback functions.

Just my two cents.

    Kevin> Kevin

\cle