Kross Namespace Reference

---

Detailed Description

The Kross scripting bridge to embed scripting functionality into an application.

• abstract API to access the scripting functionality.
• interpreter independend to be able to decide on runtime if we like to use the python, kjs (KDE JavaScript) or whatever scripting interpreter.
• flexibility by beeing able to connect different scripting interpreters together into something like a "working chain" (e.g. python-script script1 spends some functionality the kjs-script script2 likes to use.
• transparently bridge functionality wrappers like Kross::KexiDB together with interpreters like Kross::Python.
• Introspection where needed to be able to manipulate behaviours and functionality on runtime.
• Qt/KDE based, so use the extended techs both spends.
• integrate nicly as powerfull scripting system into the Kexi application.

Author:

Sebastian Sauer

See also:

http://www.koffice.org/kexi

http://www.dipe.org/kross

Namespaces
namespace	Api
namespace	Python
namespace	Ruby
Functions
void	krossdebug (const QString &s)
void	krosswarning (const QString &s)

---

Function Documentation

void Kross::krossdebug

(

const QString &

s

)

Debugging function.

Definition at line 26 of file krossconfig.cpp.

void Kross::krosswarning

(

const QString &

s

)

Warning function.

Definition at line 31 of file krossconfig.cpp.