Removal of kjsembed from kdelibs
Dominik Haumann
dhdev at gmx.de
Mon Jul 16 14:38:54 BST 2007
On Monday 16 July 2007, Harri Porten wrote:
> On Mon, 16 Jul 2007, Christoph Cullmann wrote:
> > If you convert the katepart code to QtScript, I am fine. Thought I must
> > add, QtScript in Qt 4.3 was lot slower than kjsembed for the important
> > calls to the C++ API of KatePart. Scripts in Kate were 4 times faster
> > in kjsembed than in QtScript, as their runtime is dominated by the
> > calling costs in most cases :(
>
> Are you using kjsembed? Or kjs directly? Using the latter will give you
> an even greater efficiency and kjs is very well maintained. If it's too
> complicated let me know. For 4.1 we'll add a convenient C++ wrapper API
> as discussed with Apple. They have done the same for C.
We are using kjs directly. We talked about it at akademy and jowenn and me
were of the opinion to stick with kjs for now, and after all it really
works pretty well now (and is much faster).
Scripting capabilities in the kate application should probably use qtscript,
though (but that will not happen in near future anyway).
Dominik
More information about the kde-core-devel
mailing list