Removal of KEdit

[Neil Stevens]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday April 19, 2003 08:08, David Leimbach wrote:
> Seems like it might be possible, somewhere, sometime down the road to
> clobber all 3 text editors
> just enough to get the unified feature set of all of them into one
> great text editor.  I remember bidi being a problem
> in Kate way back when I first got my KDE commit bit.    If we haven't
> found an easy solution yet it may be that
> the design of Kate is just such that it may have hit a wall in terms of
> design.  No offense intended to anyone
> involved with Kate... its a killer application in my book :).  Its just
> that I want to see it be the only editor KDE users need to have.
>
> Its pretty clear until something like that happens that KEdit must stay
> for bidi functionality.  We can't alienate that
> group of people who may use KDE who need it.

Of course there's nothing wrong with adding features to one editor, trying 
to meet everyone's needs.  But why must KDE be zero-sum?  Why must we 
remove one app when features are added to another?

The K menu argument doesn't hold water.  KAppfinder puts more editors in 
the K menu than KDE does, and the K menu backend just got rewritten to 
more easily support adding GNOME apps into the mix.  Remvong KEdit simply 
makes no difference.

- -- 
Neil Stevens - neil at qualityassistant.com
"The shepherd drives the wolf from the sheep's throat, for which the
sheep thanks the shepherd as a liberator, while the wolf denounces him
for the same act as the destroyer of liberty." -- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+oZCnf7mnligQOmERAsGpAJ9BgV+AmG9Hng4iltZO9lov2ULHEQCfbYNu
dIijI2Wg+3KpkazhKIx/abE=
=ypu0
-----END PGP SIGNATURE-----