From kde-core-devel Fri Mar 31 14:55:59 2000 From: Don Sanders Date: Fri, 31 Mar 2000 14:55:59 +0000 To: kde-core-devel Subject: Re: Moving kfind to kdeutils X-MARC-Message: https://marc.info/?l=kde-core-devel&m=95451459430941 kedit and kwrite are slightly different beasts. For instance (last I looked) only kwrite supports syntax highlighting while only kedit supports paragraph based word wrapping and spell checking. kwrite seems to be a programmers editor while kedit is a non-programmers editor. kedit is just the thing for the text editor in KMail and IMHO Konqueror. I definitely would like proper word wrap in Konqueror (when entering text in forms) so please use a QMultiLineEdit based class, it has unlimited undo/redo and better keyboard handling now too. So I'm saying kedit is essential, and should be kept in the libs. BFN, Don. On Fri, 31 Mar 2000, Simon Hausmann wrote: > On Fri, 31 Mar 2000, David Faure wrote: > > > On Fri, Mar 31, 2000 at 02:20:38PM +0200, Michael Koch wrote: > > > Am Fri, 31 Mar 2000 schrieb Stephan Kulow: > > > > Matthias Hoelzer-Kluepfel wrote: > > > > > > > > > > Hi, > > > > > > > > > > any objections? kfind makes not too much sense in kdebase, > > > > > IMHO. I would like to move it. > > > > > > > > > Well, moving kwrite to kdelibs and amor into kdebase then ;) > > > > kfind was always a good extension to kfile and konqueror, but > > > > I'm not too sure if kfile still calls it - and konqueror could > > > > look for it in case :) > > > > > > It would be great to move libkwrite (not the whole kwrite) to kdelibs for > > > compile issues. Many apps will need it. It is a fault for an app to depend on > > > kdeutils to compile. Kdevelop, KSql, KBackpage will definitly use it and I > > > think there are some others too. For distribution then we can split it e.g. into > > > kdelibs and kdelibs-utils, but remaining it in kdeutils is wrong. > > > > Glad you finally see that ;-) > > Should I move it ? > > Then we could get rid of kdelibs/kdeui/kedit.* ? :-) > > > Ciao, > Simon