Kross Namespace Reference
Namespaces | |
| namespace | Api |
| namespace | Python |
| namespace | Ruby |
Classes | |
| struct | RubyType |
Functions | |
| void | krossdebug (const TQString &s) |
| void | krosswarning (const TQString &s) |
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.
- TQt/KDE based, so use the extended techs both spends.
- integrate nicly as powerfull scripting system into the Kexi application.
Function Documentation
◆ krossdebug()
| void Kross::krossdebug | ( | const TQString & | s | ) |
Debugging function.
Definition at line 26 of file krossconfig.cpp.
◆ krosswarning()
| void Kross::krosswarning | ( | const TQString & | s | ) |
Warning function.
Definition at line 31 of file krossconfig.cpp.