Hello John,
Thank you for your fast answer!

>cbind is a very good thing.  But it isn't magic.  You might have to
>fiddle with its output when rebinding something complex.
>  
>
So, like with SWIG, there would be a lot of tweaking to do I presume. 
That's what
I expected, but you saying that "cbind is a very good thing" is a 
necessary step
before trying to use it :)

Indeed the official doc says "It is only available for Solaris, IRIX and 
Windows",
and "This facility is not fully integrated into the 6.2 release".

Do you konw if it is *really* only working on these 3 platforms ? (due 
to some platform-dependant parts ?)
Or has it only been tested on these platforms ?
How about POSIX / MacOSX ? (Mac is a requirement for us...)

>Having read the sources for wxWindows and GTK+, I would look at GTK+.
>Many think highly of wxWindows.  But, in my opinion, GTK+ is better
>engineered.  I have no experience programming GTK+ on Windows or Mac,
>but it is available in some form.  Allegro 6.2 ships with an
>experimental cbinded GTK+ interface tested on Linux.  I spent several
>weeks programming it.  It seems to work.  I also found the GTK+
>documentation and code much easier to read than wxWindows.
>  
>
I see. I'll look at your GTK+ interface. I don't know GTK+ much so I 
have no real opinion about it.
WxWindows hasn't a perfect design indeed, but really has a lot of 
functionalities
(I tried wxPython, it's really nice - I think it's the proof that with a 
good binding wx is a nice option -
alas there is no binding for CLISP except the (old ?) wxlisp - and wxcl 
which is a new project ).

>Consider asking on comp.lang.lisp.  This is a pretty inert mailing
>list.
>  
>
OK, I'll ask the same questions there!
Thanks a lot for the tips,

Rodolphe Saugier