[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gcl-devel] Re: GCL/GTK
Re: [Gcl-devel] Re: GCL/GTK
27 Aug 2003 16:27:34 -0400
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Greetings, and thanks for your reply!
address@hidden (Tim Daly, Jr.) writes:
> Camm Maguire <address@hidden> writes:
> > Greetings! Am very interested and you beat me to it! I saw your name
> > connected with this just a few days ago somewhere on the web, and have
> > been meaning to ask you about it.
> > A few questions:
> > 1) Is this the 'latest and greatest"? AFAIK, there have been several
> > attempts at a common lisp interface to gtk, mentioned on cliki I
> > believe.
> There are two major GTK bindings in the CL world that I know of:
> CL-GTK, and CLG. CL-GTK does RPC over a socket or pipe, and CLG uses
> UFFI. I like the CL-GTK approach, personally, so it's what I play
> with. The version on tenkan.org is the newest (that compiles) that I
> know of.
This seems better for GCL at present too, as UFFI looks like some
> > 2) Any experience using this with glade?
Thought I read about this somewhere. I do vouch for this tool as a
great way to build GTK guis.
> > 3) I'd like to import this into CVS HEAD. LGPL fits in perfectly with
> > GCL. Would the author like to volunteer as a GCL developer and
> > maintain this subtree? It might facilitate keeping things
> > current.
> CL-GTK is LGPL; you can import it into any CVS you want. I hardly
> maintain my personal CVS of it, so I'm not about to volunteer to
> maintain anybody else's. CL-GTK is meant to be as CL implementation
> independant as possible, so I see no particular reason for it to be in
> the GCL CVS unless the GCL developers are planning to maintain it, or
> at least mirror development elsewhere.
I agree in general that it would be odd to include in GCL proper, as
then where does one draw the line with lisp libraries? On the other
hand, given the current state in the lisp world where every library
needs to be separately compiled for each implementation, leading to
many user questions of the order of 'how do I use 'foo' in GCL', it
might make sense to ship prebuilt interfaces for some common tasks.
There's xgcl for example. And gcl-tk. We are also considering an MPI
interface. I'm raising this point here to solicit opinions regarding
what would be a well justified, logical set of libs to ship with GCL
proper. We could expand the Debian GCL package, for example, to build
other binary packages containing just the pre-compiled library modules.
> The original author of CL-GTK is Gilbert Baumann, and he certainly
> knows the ins and outs of it at least as well as I do. I of course
> cannot speak for him.
Do you know how to reach him?
> Gcl-devel mailing list
Camm Maguire address@hidden
"The earth is but one country, and mankind its citizens." -- Baha'u'llah