Rodolfo Conde Martinez <rcm(a)gmx.co.uk> writes:
Maybe i cant still say this as i dont know very well the xemacs
internals
now, but i think that before saying we gotta modify the core of xemacs to
have it benefit from stuff like Kio we should start coding, i really
think we wont need to change the core xemacs, just the Gui and add maybe
some wrappers in that Gui to filter stuff, but trying to make xemacs dont
see that its talking to something diferent from what it has always "know"
:)...
Just so there is no duplicated effort, I wanted to let everyone know that a
friend of mine is actively working on the Qt port. Right now it actually
brings up a GUI and you can almost use it.
He just dropped me another tarball last night that is synched with the
current CVS, so I think I'm going to go ahead and make a branch for it. I
will add the configure mucking to not work against Qt/Win or Qt/Mac
(neither of which I have on my machines here at home). I still think that
is kind of
This currently works with X11, Mac, and embedded versions of Qt. Seeing
XEmacs with graphics on the console is kind of freaky. :)
We have to decide what to call it though. Sam & I talked about this a bit,
and we agree that QXEmacs is decent (pronounced Queasy-Macs). Any
objections?
I'll call the branch DEV_QXEMACS. I'll post a full announcement after I
get the configuration hacking done to satisfy everyone and checked in.
-bp
--
Ceterum censeo vi esse delendam