Zack Rusin zack at kde.org
Mon Oct 7 04:58:14 BST 2002

Hi everyone,

I'm moving our discussion to kde-core-devel. 
To get everyone up to speed, the idea is pretty simple - our KTextEditor 
interfaces are too primitive to produce a robust text editor. To be 
more exact we were working on getting KTextEditor working in KMail for 
3.2 but the thing is that KTextEditor wouldn't provide many things we 
want, like : coloring quoted text like we do in the readerwindow, 
incremental spell-checking (underlining over misspelled words) - 
more-less all rich text editing capabilities. So we're left with two 
choices :
a) work with another text editor (KRichTextEditor or KoText),
b) work on fixing KTextEditor and then porting KRichTextEditor or KoText 
derivative to the new interface,

I want to do the second one and I'd like to hear your opinion. First of 
all do we all agree that KTextEditor needs to be expanded to cover more 
robust text editing capabilities? Or do you guys think that it should 
stay the way it is and people who want to have rich text editing 
capabilities should use other things?
If I get enough voices against expanding KTextEditor I'd be happy to 
work with KRichTextEdit or KoText. But we have to decide what to do 
with KTextEditor - the idea behind it was to unify the text editing 
among KDE application, but currently needs of most applications go way 
beyond KTextEditor interfaces ( which so far has been mostly directed 
towards code editing). 


Don't think that a small group of dedicated individuals can't change
the world; it's the only thing that ever has.

More information about the kde-core-devel mailing list