Re: Another XEmacs/Gtk status report... (and a poll)
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
Sorry about the duplication between -mule and -beta but the Gtk
crowd
and the Mule crowd seem likely to be moderately disjoint sets.
>>>>> "-BP" == William M Perry <wmperry(a)aventail.com>
writes:
-BP> Well, I have a XEmacs that runs using the gtk event loop
This is very cool!
-BP> Do people think a font menu is worth it? I can work around
-BP> it in Emacs/W3 somehow (I hope :). The font menu would be
-BP> replaced with a real font selection dialog box as well.
-BP> Thoughts, flames, opinions?
Oh, yeah ... I noticed that the font selection dialog image you posted
did list charset registries ... which reminds me. I was recently
browsing the Gtk documents (that I could find - libgtk-doc or some such
package in Debian GNU/Linux), and noticed that they are still even more
incomplete about I18N and rc files (except for a scary reference in NEWS
or ChangeLog that "internal representations of multilingual strings
aren't decided yet") than XEmacs's are.
Well, it boils down to using the same primitives underneath. The actual
redisplay gets done with gdk_draw_text, which uses XDrawString or
XDrawString16 depending on the font that gets passed in. It uses
XmbDrawString if you pass in a fontset instead of a font.
The only place that gtk_* will actually be used is in the widget
representations. That may take a while to catch up to mule.
What are the odds that Gtk is going to work and play well with Mule?
Anybody have an opinion?
I haven't had the nerve to try a mule build yet, I just got to the point
where I can see iso8859-1 (occasionally) in the text widget. :) Baby
steps.
I am going to put some preliminary patches up on the web site this
afternoon. The set I put up there last night are nowhere near as
functional as the stuff I've been hacking on this morning.
If Gtk is going to be futzing around with string representation, you
might want to take a look at getting Ben's Eistring stuff into your
Gtk-XEmacs as early as possible.
Ben, are you planning on putting Eistring into 21.2? Or is that a 21.3
thing? Since I went the route of writing a new device class, it should be
much easier to get up into 21.2-land.
Someone is wanting to hack on the menu stuff this weekend, so I'm going to
concentrate on the redisplay weirdness (I'm not seeing all the expose
events or something weird like that - unmap & then map the frame and
everything displays, but if you hit C-l only the line you are on shows up,
everything else just clears to the background color of the frame -
strange). I'm hoping that by early next week I can start with the
business of actually writing the language interface, or perhaps the dialog
stuff first.
-Bill P.