While we have been trying to advertise kross, we have been from being successfull so far. But I think we are making some progress lately, so I will speak once again about kross.
What is it ?
The Kross scripting bridge to embed scripting functionality into an application.
abstract API to access the scripting functionality. Here are some of it’s key feature:
- kross is independent of the interpreter, it currently supports python and ruby, but kjs/kjsembedded is planned and maybe java too
- Qt/KDE based, so use the extended techs both spends. It’s a very important poin, kross is not dependent on libkoffice, from discution I had on irc, it seems that among the few people aware of it, they believe that it can only be used in a koffice application.
- integrate nicely and easily as powerfull scripting system into any kpart application (it’s less easily and nicely if your apps is not kpart based)
How to use it ?
It’s easier, if you are appplication is kpart based, as in this case, you can use the kpart plugin mechanism and follow the tutorial here. The hardest part is to define the API you want to expose to your users, but it is common to all scripting engines.
Where to find more information about it ?
It’s funny that while we fail to make the KDE and KOffice developers community to be aware of what kross is, its fame has spread outside the boundaries of KDE, with a post in python’s mailing list.
But the current best source of information is kross.dipe.org.