Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
lablgtk for Win32
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2001-01-06 (21:05)
From: Chris Hecker <checker@d...>
Subject: Re: lablgtk for Win32

>Does anyone have any experience of using lablGTK on Windows? It seems like a
>very powerful system, but gtk itself doesn't seem to be very actively
>supported on Windows.

I'm trying to get it working now.  I was having a bunch of problems with labltk hanging my Win9x laptop after running apps from the command line (or emacs) a few times, so I decided to check out lablgtk rather than attempt to find the problem.  :)  I've got most of the examples working with the toplevel, but a few crash (not sure why yet, but I think it's problems with the way I built it...the win32 makefile isn't kept quite as up-to-date as the linux one so I've had to manually hack on it).  I also have the lablgl stuff working with it, sort of.

I don't have the compiled versions working yet.  The combination of msvc's lame compiler command line and storing the absolute paths and the cclib parms of libraries in .cm* files turns out to be a pain, and I'm running into command line length limitations on Win9x with the cl.exe that ocamlopt spawns (so there's nothing I can do about it, except maybe hack the ocamlopt sources to create a response file or something).

In general, while I'm all for cross platform gui libraries in theory, I'm coming to the conclusion that they're just not ready for production work.  Your app is huge because it's not taking advantage of any of the built in controls, it's slow to display because it's huge and because it draws all the controls itself, you can't just distribute a single exe because it needs a zillion dlls (or you end up staticly linking the 5 MB of gui dlls), and it's sloppy looking because things aren't tunable to be "just right".  Not sure what to do about it, though.

I don't need a lot of widgets and whatnot for my stuff, so I may just write a simple single-window thing that sends mouse and key events to the app, and be done with it.  Seems like a waste of time when there are these other libraries, though.  For what it's worth, Swing for Java has the same problems...he apps take 100 years to load and they don't act clean or tight once they are loaded.