From kde-core-devel  Sat Jul 22 21:18:01 2006
From: Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date: Sat, 22 Jul 2006 21:18:01 +0000
To: kde-core-devel
Subject: Re: kutils/KEdit
Message-Id: <200607222318.04439 () erwin ! ingo-kloecker ! de>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115360315811230
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart39786196.sDHspqIrxx"

--nextPart39786196.sDHspqIrxx
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 21 July 2006 16:33, Robert Knight wrote:
> Hi,
>
> The only reason I use KEdit from time to time is because it starts up
> more quickly than the alternatives (or at least feels quite a bit
> quicker) and because it is simple.
>
> If KWrite could start instantaneously, and if the menus could be
> simplified a little bit then I wouldn't mind if KEdit was dropped.=20
> To explain what I mean about the menus, the "Tools" menu is longer
> than the default window height of the whole program.  If I should
> accidentally mouse over the encoding menu, it expands to fill the
> whole screen and part of a second menu.
>
> On a side note, what is the difference between KWrite and Kate?

The editor part (KPart) is the same, but the GUI is obviously different.=20
KWrite is basically KEdit with KatePart (or whatever it's called) as=20
editor widget.

> Or in other words, when would I want to use KWrite instead of Kate?

I use KWrite when I quickly want to edit a single text file. (You'd=20
probably use KEdit in such a situation.) I use Kate (with the new great=20
support for sessions) for different tasks that require editting more=20
than one file.

Regards,
Ingo

--nextPart39786196.sDHspqIrxx
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBEwpYMGnR+RTDgudgRAokBAKCWdxHqj2I+cRguyLMl1uLnw4oUtgCfbTUi
XB5yb006HAU5Ucb9W8+4MuE=
=CzSg
-----END PGP SIGNATURE-----

--nextPart39786196.sDHspqIrxx--