From kde-core-devel Tue Jan 10 23:54:32 2006 From: Richard Moore Date: Tue, 10 Jan 2006 23:54:32 +0000 To: kde-core-devel Subject: Re: KHTML, KJS Unfrozen -- details Message-Id: <5491a5150601101554n2ab0bb13ge47dc67e4caa45b2 () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113693728019375 MIME-Version: 1 Content-Type: multipart/mixed; boundary="------=_Part_9302_4882218.1136937272210" ------=_Part_9302_4882218.1136937272210 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 1/10/06, Joseph Wenninger wrote: > > Is there a chance that KJSEmbed is going (soon) to be moved to kdelibs, > if > KJS should not be used directly anymore ? Or will it still stay in > kdebindings ? I think that the core part of KJSEmbed (ie. the wrapper around the interpreter) can be moved to kdelibs relatively easily. Now that we have Ia= n Geiser's new design for the bindings code, this can be kept more loosely coupled, so it would be possible to hold it in another module. That said, the discussions in Malaga resulted in agreement that we should integrate KJSEmbed tightly into applications (eg. as is already planned for Plasma, see Zack's work on Dashboard compatibility as an example). Together this implies that KJSEmbed should be in kdelibs, though possibly without full access to all of the Qt/KDE apis. Rich. ------=_Part_9302_4882218.1136937272210 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

On 1/10/06, = Joseph Wenninger <jowenn@kde.org> wrote:
Is there a chance that KJSEmbed = is going  (soon) to be moved to kdelibs, if
KJS should not be = used directly anymore ? Or will it still stay in
kdebindings ?
 
I think that the core part of KJSEmbed (ie. the wrapper around the int= erpreter) can be moved to kdelibs relatively easily. Now that we have Ian G= eiser's new design for the bindings code, this can be kept more loosely cou= pled, so it would be possible to hold it in another module. That said, the = discussions in Malaga resulted in agreement that we should integrate KJSEmb= ed tightly into applications (eg. as is already planned for Plasma, see Zac= k's work on Dashboard compatibility as an example). Together this implies t= hat KJSEmbed should be in kdelibs, though possibly without full access to a= ll of the Qt/KDE apis.
 
Rich.
 
------=_Part_9302_4882218.1136937272210--