KDevelop editor interfaces

Ralf Nolden nolden at kde.org
Mon Apr 23 10:55:01 UTC 2001


Matthias Hoelzer-Kluepfel wrote:
> 
> Am Sonntag 22 April 2001 17:51 schrieb Cullmann Christoph:
> 
> > Hi, the problem with a interface in kdevelop will be that it can't be
> > implemented by any editor app, because the app must link to the interfaces
> > lib which is in the kdevelop package -> the app won't run or compile on
> > system without kdevelop :(
> > Of course you can say, the apps could implement it and the parts will be
> > add to the kdevelop cvs -> same problem like old kwrite.
> 
> Christoph, this just means that once the interface is working and tested, it
> will have to be moved to kdelibs :-)

Christoph and I had a discussion about this last night on IRC. He's
working on it to make the interface usable and as generic as possible,
and I also told him that it has to end up in kdelibs as a real
texteditor interface replacing the current one. 

As far as Kate itself goes, we discussed about that and I really don't
see the point of it's development. It just makes the user more confused
if he has a half-ide-like app (kate) and an IDE with kdevelop who's idea
is to fullfill exactly the same requirements and abilities. The plan
behind kdevelop 3 (2.0 originally before gideon) was to make it a loose
framework where we can write plugins for all languages so it can be used
as a complete IDE for those, including HTML and PHP. I don't quite see
the point that the kdebase module ships kate then if kdevelop does the
same job in it's minimal version. I know that christoph quite doesn't
like the idea, but that was the target even before kant/kate showed up
and I don't know who made the decision to put it into kdebase as from
the user's point of view I would say it's more confusing than helpful. 

Christoph, please think about it. We've already talked about double work
and we had similar situations throughout the years. Out of experience I
can tell, that it doesn't make much sense and so I'd like to invite you
to put your experience into the generic framework of kdevelop/gideon to
do that what you're doing now with kate as it can/will do it anyway.
Take the time you need to do this decision for yourself, but bare in
mind that openness towards ideas is the way to go, and you're definetly
not lost in our team as it's part of KDE like you're with kate now
anyway.

Cheers,

Ralf
-- 
Finally, even I have to admit that being myself was the best thing
that ever could have happened to me. - Le Grand Charmeur

**********************************
Ralf Nolden

The KDevelop Project
http://www.kdevelop.org

nolden at kde.org
rnolden at kdevelop.org
**********************************


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop-devel mailing list