[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kedit vs. kwrite
From:       David Sweet <dsweet () chaos ! umd ! edu>
Date:       1999-02-04 15:07:38
[Download RAW message or body]

On Wed, 03 Feb 1999, Peter Silva wrote:
>uwe@uwix.alt.na wrote:
>> 
>> On Wed, 3 Feb 1999, Roberto Alsina wrote:
>> 
>> > On Wed, 3 Feb 1999, Jacek Stolarczyk wrote:
>> >
>> > > On Wed, 03 Feb 1999, Stephan Kulow wrote:
>> > > [...]
>> > > >OK, Text Editor and Programmer's Editor.
>> > > These two seem good, but let me say that I dislike the idea of
>> > > replacing kedit with kwrite. And it's not only about printing
>> > > capabilities. Let's use the tools appropriate to the needs. KWrite has
>> > > smart syntax highlighting and should be the default app for all sorts
>> > > of source code files, but not necessary for editing/reading ChangeLogs,
>> > > README's or writing a short cvs commit message. Kedit nicely fits for
>> > > this task and is one third smaller (binary size). I simply don't like
>> > > when when on 80% of launches of an app I use (always the same) small
>> > > part its possibilities. It just indicates that another smaller tool is
>> > > needed - kedit in this case.
>> >
>> > Last time I checked, kwrite also had some other advantages over kedit:
>> >
>> > 1) It works better with large files
>> > 2) Has undo
>> >
>> > Those two things make a lot of difference, at least to me.
>> 
>> Additionally: If you work a lot with c&p in kedit it tends to start
>> to auto-select parts of the text all of a sudden. But then, this
>> could be an Alpha problem.
>> 
>
>OTOH, Kedit has spell checking integrated, which (last time I looked,
>two months back) kwrite didn't.
>
>
>-- 
>Pete

I'm working on integrateing spellchecking into kwrite.  It seems like too big a
change for 1.1 though, so look for it afterward.

David

[prev in list] [next in list] [prev in thread] [next in thread]