On 2 May 2002, Stephen J. Turnbull wrote:
>>>>> "PB" == rendhalver
<rendhalver(a)xemacs.org> writes:
PB> i was under the impression that you do need to use qt for KDE
PB> apps or is there some kind of funky abstraction thingy which
PB> lets you get around it some how ??
You do probably _link_ (indirectly) to Qt (see below). But what these
guys are saying is that XEmacs probably only needs to do #include
<kde/kpart.H>. Since KDE is already GPL, they have already taken care
of the legal issues. (NB. If they got the legalities wrong, rms
would make us a codefendent with KDE anyway. ;-)
Even if KDE has an exemption for linking with QT (which I assume it does,
since someone ported KDE to Windows, I believe), XEmacs would also have to
have the exemption (which it won't have, from what I gatter). KDE links
with OpenSSL, so I don't think we should trust them to do the legalities
right.
To do a KPart, XEmacs need to link with Qt, so the license issue is always
present. XEmacs would probably not have to support Qt as a widget library
though. Of course, it may turn out that doing a KPart without supporting
Qt widgets is unusable, but at least we can try.
Having a big application link both with GTK/GNOME and KDE seems fun.
(The output from "ldd xemacs" is starting to be rather small compared to
other applications... and we surely can't have that.)
Btw, from
<
URL:http://216.239.39.100/search?q=cache:-JJLRNKV4FkC:www.kdevelop.org/%3...
on KDevelop 3 issues:
Emacs editor integration - not yet started, no activities
It is removed from the current page though, replaced by
<URL:http://fara.cs.uni-potsdam.de/~smeier/www/?filename=current_work.html&set_lang=en>:
Vim editor integration - waiting for kvim to implement the KTextEditor
interface
Interesting.