Re: Qt Xemacs ??

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. ;-) The same goes for the technical issues of managing any window-dressing (literally in this case, see src/ExternalShell.c for an idea in Xt terms of where the Qt stuff might have to come in) widgetry. As I understand it, where we have to create our own Motif/Xt/native Xlib widgets, the idea of KPart is to provide a standard KPartShell widget. This would provide a clean API for XEmacs to hook into, and might possibly be implemented without a linkage to Qt, but I wouldn't bet on it. At the very least I bet you include header files for atoms and structures (a la the Xmu stuff) and stuff. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py