faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Model KWrite after GEdit, keep Kate for geeks
by Tray on Tuesday 15/Apr/2008, @10:11
|
I'm certainly not a GNOME partisan, but when it comes to fitting the needs of the average user, GEdit is by far better than KWrite. Getting rid of all the programming-specific options like "Code Folding", "Switch to Command Line", "Highlight range between selected brackets", different colors for "Base-N Integer", "Modes & Filetypes", and the "Select to Matching Bracket" keyboard shortcut, as was apparently discussed in this meeting, is a great step toward making KWrite a general-purpose simple text editor. But this is going to be hard, because niche settings for programmers are spread everywhere in KWrite's menus and configuration system.
There is also extreme redundancy and confusion about shortcuts. For example, Settings-> Configure Editor -> Shortcuts lists a whole bunch of keyboard shortcuts (such as "Select to Matching Bracket") that don't even appear when the user goes to Settings-> Configure Shortcuts. And vice-versa, shortcuts in Settings-> Configure Shortcuts such as "Undo" don't appear in Settings-> Configure Editor -> Shortcuts.
By the way: does the "Show Path" option under the Settings menu do anything in KWrite? |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
|
Over 40 comments listed.
Printing out index only. |
Re: Model KWrite after GEdit, keep Kate for geeks
by Robert Knight on Tuesday 15/Apr/2008, @11:05
|
> I'm certainly not a GNOME partisan, but when it comes to fitting the needs of the average user,
Who needs a text editor but isn't a programmer or system admin? Who regularly edits text files which do not have some form of syntax or grammar designed for software to process?
Gedit, Vim, Emacs et. al are called "text editors" but I cannot remeber the last time I edited a large body of something that was just plain text. In other words, something that wasn't a config file, code or other structured data (eg. XML). The one exception that springs to mind being people who use Emacs as their mail client.
Most of the non-programming text I write is done via embedded editors in my mail client, web browser, IRC client etc.
|
[
Reply To This | View ]
|
|
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Ilyak on Tuesday 15/Apr/2008, @11:27
|
I am a programmer and use kate regularily.
I need all that.
I've never seen non-programmers to use a text editor.
They're comfortable with either oowriter or textarea.
So, please, don't try fixing thing that isn't broken.
|
[
Reply To This | View ]
|
|
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Ilyak on Tuesday 15/Apr/2008, @11:29
|
Oh, nevermind, I've missed your point entirely.
I don't see why there's kate and there's kwrite. You're prodadly right, however we'll need to ask people who actually use kwrite.
Also: it would be cool if kwrite could embed into konqueror as textarea.
|
[
Reply To This | View ]
|
|
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Niklas on Tuesday 15/Apr/2008, @15:43
|
Why not using Kedit? Or another simple Texteditor (kde-apps.org) if you are confused by too much options? Why ripping an excellent program? To achieve the 10th simple one?
It would be a big mistake with sadly consequences for KDE to follow those false recommendations!
I wonder who could be interested in this ...
|
[
Reply To This | View ]
|
|
|
Re: Model KWrite after GEdit, keep Kate for geeks
by KA on Wednesday 16/Apr/2008, @22:12
|
+1
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
