wmperry(a)aventail.com (William M. Perry) writes:
> - Gnome and/or KDE integration
It's a fundamental flaw in their design if they cannot deal with
applications that are not written using their specific toolkit. Not having
session management in kwm just because XEmacs doesn't use Qt is really
lame. Or has that been fixed?
Nope. And I won't do it, cause I had epileptic seizures after I browsed the
source of KDE (and part of the Qt docu) in search of their DnD protocol (they
use a version 0 OffiX). But this might come from my natural aversion against
code written is this language.
I want KDE to do DnD with XEmacs (who knows OffiX already), but KDE can't find
the window of XEmacs, cause Qt hides the windows from KDE (in QMouse events)
and so it has to do the search on it's own... (same problem as the session
stuff, kwm does not know XEmacs).
> - Real dialog boxen. Replace, for instance, should not
use the
> modeline when invoked from the menu but create a nifty dialog box.
It would be nice to just do this in normal emacs frames... then all
operating systems get them.
Yes, native looks require lot more work (ask the NT team about this...)
> - Eventual ditch of the infamous Lucid stuff. Or will you
implement
> teardrop menus, detachable toolbars, themeable widgets elements,
> etc... ?
>
> You will have a *lot* of work if you want lwlib to reach the level of
> what is expected from toolbars, menus and scrollbars nowadays.
This is a good reason... eventually. I think we have bigger fish first.
But then everyone's time is their own to hack what they wish. I'll be
doing the module support again soon, even if nobody every wants to use it
but me. :)
What is module support? Never heard about it (shame on me).
Regards,
Oliver.