Removal of KEdit

Maks Orlovich mo002j at mail.rochester.edu
Sat Apr 19 21:10:46 BST 2003


On Saturday 19 April 2003 03:55 pm, Aaron J. Seigo wrote:
> On Saturday 19 April 2003 03:50, Stephan Binner wrote:
> > I want to propose the removal of KEdit from KDE releases: KWrite is a
> > good lightweight editor.
>
> wrong. evidently all the programming you and others have been doing has
> clouded your vision when it comes to text editors. KWrite is a
> *programmer's editor*. it's more complex than most users need or want. 

It's actually not that - it's a meta-editor; which can embed different text 
editor components.(ed. which you apparently do know very well; but let's keep 
it ;-) ) Perhaps an interesting option would be to turn kedit into an editing 
component and make kwrite embed that and not katepart by default. (The menus, 
etc., are configured based on how many interfaces the editor supports, 
AFAIK); or may be to provide a different 'virtual' katepart version that 
provides regular-user type features.

>  o Proper i18n support: that means BiDi and multibyte input. Neil has
> already gone over that extensively and is 100% correct.

Multibyte input is just fine, AFAIK; although I don't know where the encoding 
command line option has went off too ;-)

>
>  o A simplified interface that doesn't include things like indentation and
> syntax highlighting options. Yet another wrapper around the
> ktexteditorinterface that provides a KEdit-like simple interface would
> suffice, but that's not written let alone maintained yet.

Or the other way around/backwards.

> both of the above are fixible, but the answer is not to drop KEdit, it's to
> address the audience and problem space that KEdit does with new code. that
> an a move of Kate as i cover below.
>
> > Nobody installs kdeutils for KEdit.
>
> the real question is: does anybody use it?

Side question: why does anyone install kdeutils? It's the least well-defined 
of our modules. (No, I am not sure I want that subthread/digression either 
;-) )

> > It's often critized that default full installation has 3 editors.
>
> if you want a real solution, move Kate and/or KWrite (the applications) to
> kdesdk where they belong. they programmer's editors, kdesdk is programmer's
> tools. if one moved Kate to kdesdk then voila! two text editors in the base
> install of KDE for non-programmers.

BTW, weren't there plans to setup a Kate module as it grows in its power? Any 
news on that? On the other hand, it seems many people install kdesdk even 
when they're not developers - witness the confusion over cervisia's konqui 
integration.






More information about the kde-core-devel mailing list