Marcus Harnisch writes:
First of all, I would like to second the idea of switching to a
single cross-platform toolkit.
It's a nonstarter until you tell us "What are the candidates?" AFAIK
Xt is as close as it gets; we can't ask people to build GTK on Solaris
or Mac or Windows, and not everybody is willing to use MacPorts or
Cygwin. Emacs hasn't found a satisfactory "cross-platform" toolkit,
and they're still adding more toolkits (Cocoa/NextStep). Another
question is how do these cross- platform kits deal with native
I am thinking of itches like the stupid Xft display residue
and the like.
Xft is nowhere near cross-platform though. "Cross-platform" is a hard
problem, apparently harder than you think it is.
A proper print dialog!
Don't Windows, GTK, and Carbon all have the native dialog?
Font selection using a slightly less arcane interface than
comes to mind.
Sure, I'm working on that. That's one of the main reasons I don't
really consider 21.5 to be releasable.
Keyboard issues could be worked around more straightforward I
(might have to be worked out with XEmacs low-level handling). Since my
switch to Ubuntu I still don't get German Umlauts on a US keyboard the
way I used to in my good old plain X11 set-up.
I have no experience of what you're talking about; a full bug report
would be appreciated. Japanese requires a full input manager, and
that I know a lot about. But accented keystrokes, maybe Aidan knows,
but I don't. And I don't use Ubuntu.
> And do they flexibly allow input from other sources like
> subprocesses and TTY displays and gnuclient?
Not sure how XEmacs handles that communication.
It's at the level of select(2) .... This can be done with Xt (modulo
recent breakage in Xt's event loop). Others (eg, GTK v1, GNUStep)
tend to insist that you do it their way, which tends to break C-g
handling and things like that.
XEmacs-Beta mailing list