i think it's wrong to tout the raw gtk-* interface as the "right" interface
to
write lisp in.
in fact, if at all possible i'd suggest not exposing this at all. instead,
expand the generic interface as necessary to include new gtk features. you
could also provide an "escape" mechanism for adding or querying raw gtk
properties that are not implemented in the abstract interface, but i do NOT
want to see a proliferation of lisp code that is gtk-specific. although
creating raw interfaces may seem "easier" and more powerful, it is in fact a
classic mistake made by novice interface designers, and invariably comes back
to haunt them.
"William M. Perry" wrote:
Here is the official submission of milestone one. All documents will
also
be available at
http://www.cs.indiana.edu/elisp/gui-xemacs/
If anyone has feedback on style / structure / etc (especially my
impressions of either toolkit) please let me or the list know. It looks
like the front-runner right now is Gtk / Gnome. Next document will detail
the implementation plans and what the language bindings will actually look
like.
I am wrestling with how the bindings should actually look right now. I
personally prefer a very lispy interface using 'put' and 'get'
generically,
and something similar to libglade so that the GUI can be changed very
easily.
The first code milestone will be May 20th. I will be on vacation from my
'real' job from now until then. The main work will be in getting the
XEmacs event loop and redisplay to cooperate with Gtk. The language
binding should be fairly simple.
-Bill P.
------------------------------------------------------------------------
Name: gui-xemacs-m1.tar.gz
gui-xemacs-m1.tar.gz Type: Unix Tape Archive (application/x-tar)
Encoding: base64
------------------------------------------------------------------------
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/typing.html.