Removal of KEdit

[Christoph Cullmann]

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

On Saturday 19 April 2003 14:56, Neil Stevens wrote:
> On Saturday April 19, 2003 05:45, Jason Keirstead wrote:
> > On April 19, 2003 09:30 am, Neil Stevens wrote:
> > > On Saturday April 19, 2003 02:50, Stephan Binner wrote:
> > > > Hello,
> > > >
> > > >  It's often critized that default full installation has 3 editors.
> > >
> > > How many times must we go over this same argument?  I thought we
> > > settled this with the inclusion of Juk: Different apps with different
> > > purposes are fine.
> >
> > I fail to see what the purpose of KEdit is when we have KWrite and
> > KRichTextEdit. KWrite can do everything KEdit does, and much much more,
> > and uses the exact same resources.
>
> Well, that's not true, but if it were true, then this would just be Juk vs
> Noatun all over again, with the difference that KEdit is already IN
> kdeutils, so it already has users who rely on it being there.
>
> We can't re-argue every policy every time it comes up.
Noatun vs. Juk was about different apps for different userbases, but beside 
that KWrite has no bidi support (and until it gets that KEdit or an other 
QTextEdit based editor must stay) KWrite and KEdit are just equivalent in the 
base features. KEdit has no reason to stay beside it's bidi support. For 
convenience kedit could be a link to kwrite, to be backward compatible to 
apps starting kedit as editor (and we would need to adjust some command line 
options for kwrite I guess, not sure, have not installed kdeutils atm).

cu
Christoph

- -- 
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann at kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+oUx0yPjDGePm9UIRAur/AKCK5JBE4/bQlb9Nl+jN9+xpVZbMbQCeKSCY
AaBEKOkh84Oe5P3S57LreZM=
=tMMJ
-----END PGP SIGNATURE-----