On Tuesday 27 November 2001 10:17 am, Mickael Marchand wrote:
> why not, we could do much more thing (KTextEditor), question is where ?
> do we keep old KEdit ? (for compat)
> or simply moving KEdit somewhere else ?
>
> actually, i don't know where we could 'logically' put it,
> there is no really good place for widgets using
> interface,kpart,... in kdelibs. I guess we could have the same problem
> for other widgets later

I would leave KEdit/keditcl as is and create a new directory libktextedit=
 that=20
implements a edit-widget that dynamically loads the user's preferred=20
KTextEditor part (that's basically a single factory method) and a KSimple=
Edit=20
that implements a KTextEditor part based on QTextEdit (you could start wi=
th a=20
copy of keditcl for that)=20

I guess this factory method is simple enough to be added to libkpart. So=20
libktextedit would only contain KSimpleEdit which builds into something l=
ike=20
libksimpleedit, the default part for this factory method.

(If I recall corrrectly, that's basically what you had in mind in the fir=
st=20
place, but couldn't do because KEdit had to remain source compatible.)

We can then mark KEdit/keditcl as obsolete and schedule it's removal for =
KDE 4=20
or whenever Qt decides to drop QMultiLineEdit completely.

Cheers,
Waldo
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<