Matthias: I would recommend to not get > lost in this tough, because there are plenty of cross platform > libraries out > there that implement stuff unrelated to a GUI (threads come to mind, > etc.)
I think we are all on the same page here. One of the things we really like about FLTK is that it doesn't try to be everything to everyone. Especially with regard to non-gui related function. None of the items we have been thinking about would attempt to add any non-gui related stuff. Matthias: > supporting it. Thems made the code incredibly complex and was rarely > used. > Sure, skins are cool, but there is a very high price to pay. I agree. This would have to be done very carefully and most certainly be a build option. We are actually trying to work through the concept of a derived version of each widget with "skin" in the name (ie; Fl_SkinWindow etc.). This could then be wrapped up in a separate lib without too much impact to the original code. We, like many others, have to consider the business application angle to a degree when we're thinking about FLTK. Like it or not, skins sell software. The only thing that is cool about skins is the way they look, but creating and integrating them is a real PITA. Thanks, Gerry _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
