Components

These are the core components of Kross

The core of Kross

The core of Kross provides the framework to deal transparently with interpreter-backends and offers abstract functionality to deal with scripts.

The Kross::Manager class is a singleton that provides the main entry point to deal with the Kross Scripting Framework.

The Kross::Interpreter class is the base for interpreter implementations. Each scripting backend needs to inheritate its own interpreter and implement it. The Kross::InterpreterInfo class provides abstract information about a Interpreter before the interpreter-backend itself is loaded.

The Kross::Action class is an abstract container to deal with scripts like a single standalone scriptfile. Each action holds a reference to by the matching Kross::Interpreter created Kross::Script instance.

The Kross::ActionCollectionProxyModel class implements a QSortFilterProxyModel for a Kross::ActionCollectionModel instance which implements QAbstractItemModel to provide a model for views on a Kross::ActionCollection instance.

The Kross::ActionCollection class manages collections of Kross::Action instances.

The optional Kross modules

Kross is able to optional dynamic load modules which provide then additional functionality for scripts.

The Forms module

Kross::FormModule provides access to UI functionality like dialogs or widgets.

The KDE Translation module

Kross::TranslationModule provides access to the KDE internationalization and translation facilities.

The Kross console application

The Kross console application provides an executable application to run by Kross supported scripts from within the commandline:

kross myscript.js

The unit and regression tests

Some internal testcases used to prevent regressions. To build and run them compile with;

cmake -DKDE4_BUILD_TESTS=1 ...