Revision 758457
Go back to digest for 13th January 2008Features in KDE Base
Connect QtScript and Kross together.
1) QtScript as Kross interpreter backend;
We support now both. Kjs+KjsEmbed as "javascript" (mimetype application/javascript and file-extension *.js) and QtScript as "qtscript" (mimetype application/ecmascript and file-extension *.es).
2) Kross in QtScript as QScriptExtensionPlugin;
Each KDE-application using QtScript will be able to transparently access Kross now. Following should be possible from within plain QtScript now;
var action = Kross.action("MyPythonScript");
action.addQObject(action, "MyAction");
action.setInterpreter("python");
action.setCode("print 'hello world'");
action.trigger();
That means, QtScript is able to deal transparent with all supported scripting-backends (Python, Ruby, JavaScript, ...) now :)
See also the samples in <a href="http://websvn.kde.org/trunk/KDE/kdelibs/kross/qts/test.es">http://websvn.kde.org/trunk/KDE/kdelibs/kross/qts/test.es</a>
File Changes
- /trunk/KDE/kdelibs/kross
- /qts
- /qts/CMakeLists.txt
- /qts/interpreter.cpp
- /qts/interpreter.h
- /qts/main.cpp
- /qts/plugin.cpp
- /qts/plugin.h
- /qts/test.es
- /qts/test.py
- /qts/values_p.h
- /test/unittest.es
- /trunk/KDE/kdelibs/kross
- /CMakeLists.txt
- /core/action.cpp
- /core/action.h
- /core/childreninterface.h
- /core/CMakeLists.txt
- /core/errorinterface.h
- /core/interpreter.cpp
- /core/interpreter.h
- /core/krossconfig.h
- /core/manager.cpp
- /core/manager.h
- /core/script.h
- /test/unittest.js