Removal of KEdit

[Jason Keirstead]

On April 19, 2003 10:16 am, Neil Stevens wrote:
> > 14404 jason     15   0 22120  21m  14m R  0.0  8.7   0:00.93 kedit
> > 14615 jason     15   0 21720  21m  14m S  0.0  8.5   0:00.70 kwrite
> >
> > .. this is accurate enough for me to assume that kedit has no
> > resource usage advantage over kwrite.
>
> So it's your claim that KEdit uses 22 megabytes of RAM?

Its my claim that they both use the approximate same amount of RAM.
I know top is not a good metric, but it is equally skewed for both applications
and as such is a valid comparison.

> > noatun does not, and noatun focuses on things Juk does not. But KEdit
> > and KWrite focus on the exact same thing, plain text editing, and KEdit
> > has no advantages to offer at all over KWrite.
>
> You keep saying that but you show no evidence of that.   Right here right
> now I can't manage to get KWrite to do XIM, spell checking, or loading of
> a file with a given character set on the command line.

If you can't use spell checking in KWrite or can't load files with certain
charsets, I would suggest you have issues with your build since I can do
all this fine. As for XIM I have no idea.

> If you don't use KEdit, so be it.  But why take it away from others who
> want it?

Because its using an outdated widget and is unmaintained. If KWrite lacks
XIM then it should be added to it, we shouldnt be using that as an excuse to
keep this old outdated applicaiton.

But if for some reason KEdit is kept, it needs a  lot of work. it is not using 
the standard find and replace dialogs, and should be using KTextEdit not
KEdit for the entry widget.


-- 
Jason Keirstead, BCS
http://www.keirstead.org