[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    kdevelop (Re: Proposal to plan for "Milestone Releases" on the way to
From:       David Faure <faure () kde ! org>
Date:       2006-01-25 23:44:17
Message-ID: 200601260044.17455.faure () kde ! org
[Download RAW message or body]

On Thursday 26 January 2006 00:40, Alexander Dymo wrote:
> I've been watching at core KDE developers for three years. They still use 
> vi (emacs). Why? Looks like KDevelop doesn't have clear benefits as
> a development tool for them. This is, of course my opinion and I'd really
> like to hear from KDE developers what they think is wrong in KDevelop.

I would need kdevelop to have support for emacs-lisp, or to have at least 
all the features implemented in kdesdk/scripts/kde-emacs/ (good luck!),
but the latter would be less flexible for future extensibility...

For the emacs-lisp support, I know that it's a huge amount of work - Kalle and I
started on that one day, extracting the lisp engine and basic functions out of xemacs,
and we got to the point where a katepart could run a few simple scripts, but 
the code was painful, mainly because kate (and the KTextEditor interface) is 
line+character oriented, whereas emacs works with linear positions in one buffer... 
interestingly enough, Scribe also works that way, so maybe someone could update
that interfacing based on Qt4's QTextEdit...
But there's also interfacing with the IDE to be done (to get it to open another file,
switch to another buffer, etc.). Anyway - many ideas, but little time for them.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

[prev in list] [next in list] [prev in thread] [next in thread]