From: Duncan C. <dun...@wo...> - 2007-11-08 11:35:52
|
On Thu, 2007-11-08 at 11:33 +0100, Wolfgang Jeltsch wrote: > Am Donnerstag, 8. November 2007 03:14 schrieb Duncan Coutts: > > […] > > > * multi-platform support with native look > > Really? I thought that GTK+ paints all the widgets by itself and therefore > doesn’t get the native look completely right. Especially not on Mac OS X. It uses a combination. On Windows it uses the native theming dll to follow the theme, though yes it has to paint the classic theme itself. The native look is not 100% but it's really pretty close these days. Note that I didn't say native look and feel :-) You're right on OSX it's not close. We're waiting for the native (non-X11) GTK+ backend on OSX. That's still in development. > > * LGPL licence > > Oh, I didn’t know this. I think, this could be a serious problem. The LGPL > doesn’t allow usage of the library in proprietary software, except where the > library code is only linked with the proprietary code. I suppose that GHC > doesn’t just link different packages but uses information of used packages > during compiling. This would mean that it’s not possible to build > proprietary software with Gtk2Hs which would be bad. Please use BSD3 for > Haskell libraries! We've used LGPL because that's the license that GTK+ itself uses. If you think it's a major problem we could see about adding a linking exception to allow static linking of the Gtk2Hs library. Obviously the GTK+ C libs are always dynamically linked to satisfying the LGPL there is easy. It's not that easy to change however as there have been many contributers so it's not easy to relicence (or add an exception) as we need their consent. Another alternative (as of GHC version 6.8.x) is to build Haskell libraries as dynamic libs. That would then put us in the same situation as for the GTK+ C libs. Duncan |