Re: Model KWrite after GEdit, keep Kate for geeks

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Model KWrite after GEdit, keep Kate for geeks
by Tray on Tuesday 15/Apr/2008, @15:55

> Why not using Kedit?

Because the decision was made that KDE4 (specifically the kdebase package) will have only _one_ simple text editor that shared its infrastructure with more advanced editors in order to save memory. KEdit was therefore removed and labeled redundant (which it was), but now KWrite must live up to its goal to be simple.

> Why ripping an excellent program?

Because KWrite's purpose is to be simple, and because KDE needs a simple editor in its base package order to fill the needs of ordinary, non-programmer users.

Related Links

·   Articles on Community and Events
·   Also by Tray
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Model KWrite after GEdit, keep Kate for geeks
by Niklas on Tuesday 15/Apr/2008, @16:15

> KEdit was therefore removed and labeled redundant (which it was),
> but now KWrite must live up to its goal to be simple.

That is a really paradox! You got this, didn't you?
Kedit, the 'Simple Text Editor' was redundant - but now Kwrite has to change because it is not simple. Either the first or the latter can't be the truth.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Tray on Tuesday 15/Apr/2008, @17:41

There's no paradox.

KEdit was considered redundant because its code duplicated a lot of kdelibs/kate/ and because no one wanted to maintain KEdit's code. The redundancy did not stem from KEdit's mission to be a simple text editor.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by What the hell on Thursday 17/Apr/2008, @03:35

And you seem to forget that this is a volunteer project, who are mainly programmers and only maintain KDE because THEY find it useful. If you don't like it then get a third party editor that is simpler for you.

Oh, and yes there is a paradox, KDE has never been simple, just open KControl and look at the settings for Desktop>Window Behaviour for example, the fact that you are declaring that a highly configurable environment should have a inflexible, *non-configurable* text editor is just bizarre. If that's what you want, then use GNOME, from what I've heard, being "simple" is the whole reason GNOME continues to exist so why don't you just use your right to choose and choose that instead?

Also, to reiterate for emphasis: The only "programming" options are indentation management, syntax highlighting and code folding. Everything else IS useful for "normal" users, just because YOU don't find it useful doesn't mean no-one else does (Despite most user's complaints about bloat in MS Word, anytime MS removes a feature there are always more user complaints from people who actually did find it useful).

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Tray on Thursday 17/Apr/2008, @05:55

> And you seem to forget that this is a volunteer project, who are mainly
> programmers and only maintain KDE because THEY find it useful.

Different developers have different motivations. Some do it to because they are going to use the product themselves as you mention. Other devs do it so that users *unlike them* (ie. the rest of us) can use the software. Not everyone has selfish motivations :)

> If you don't like it then get a third party editor that is simpler for you.

With that kind of attitude, KDE will stay the desktop of choice for the couple ~200,000 programmers of the world, while other Free Software systems will be used by the remaining millions.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Madman on Monday 26/May/2008, @18:19

The desktop of choice is determined by it's text editor? Please, I think someone's getting more desperate by the minute.

I've just used KWrite, and I've found nothing intrusive. I don't even qualify as a full, "geek", as the most advanced programming I know is Javascript, but for simple text editing KWrite hasn't done anything wrong for me.

I searched for text with ease (found it easily in the edit menu without searching about for it. NOT INTRUSIVE)(now, without a separate pop-up box and instead with an integrated search bar. LESS INTRUSIVE).
The only somewhat geeky option in the file/edit menus was, "convert to HTML". In, "View", the least geeky option was at the very top (new window), while little else in there would have been useful (NOT INTRUSIVE - what the bloody-hell else could I be looking in that menu for?).
In, "tools", all the most usefull options came with pretty icons on the sides, making them clearly visible - LESS INTRUSIVE.
One thing I love to use - adding things directly from the menus to the toolbar, *removing the need to, "sift through" what little geek-speak there is in the menu time and time again*. LESS INTRUSIVE.

I wouldn't even call this a, "simple" text editor, because simple text editors (notepad) don't get this easy to use! It's powerful and, from a none-geek perspective, it does everything I need and quickly. Another bonus, I can quickly make a HTML page in it because of the coder features, *which have no reason to be gotten rid of*.

If it ain't broke, don't fix it.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"KDE is much too well-structured for this world..." -- Rob Buis
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.