Policy regarding QtWebKit and QtScript

[Christoph Cullmann]

Hi,

>> Isn't the designated successor for QtScript QJSEngine
>> (I even assumed there should be some porting tools?)
> 
> That's what I meant under 'qml engines'. :)
> 
> A relevant mail by Frederik:
> http://lists.qt-project.org/pipermail/interest/2015-June/017446.html
for KTextEditor:

1) kross is useless for it

2) QJSEngine: I tried to port with Qt 5.4, but it didn't allow for all things needed like setting up some
global functions in the engine and wrapping custom datatypes like QtScript did, perhaps this has changed
but as IMHO no porting guidelines exist, have not tried it again. (attached the state of the port,
if somebody wants to give it a try) But as the above mail indicates, such a guide should come up.

Greetings
Christoph

-- 
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH      Email: cullmann at AbsInt.com
Science Park 1                         Tel:   +49-681-38360-22
66123 Saarbrücken                      Fax:   +49-681-38360-20
GERMANY                                WWW:   http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qjs.diff.gz
Type: application/x-gzip
Size: 13282 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20151223/0d8adf2f/attachment.bin>