Kross
Kross Class List
Here are the classes, structs, unions and interfaces with brief descriptions:Kross::Action | The Action class is an abstract container to deal with scripts like a single standalone script file |
Kross::ActionCollection | The ActionCollection class manages collections of Action instances |
Kross::ActionCollectionEditor | The ActionCollectionEditor class implements a general editor for Action and ActionCollection instances |
Kross::ActionCollectionModel | The ActionCollectionModel class implements a QAbstractItemModel to provide a model for views of a ActionCollection instance that manages a collection of Action instances |
Kross::ActionCollectionProxyModel | The ActionCollectionProxyModel class implements a QSortFilterProxyModel for a ActionCollectionModel instance |
Kross::ActionCollectionView | The ActionCollectionView class shows a QTreeView where the content of a ActionCollection is displayed and optional actions to run, stop, add, edit and remove scripts are provided |
Kross::ChildrenInterface | Interface for managing Object collections |
Kross::EcmaInterpreter | The EcmaInterpreter class implements a Kross::Interpreter to provide a factory for EcmaScript instances |
Kross::EcmaPlugin | Kross QtScript Extension that provides access to the Kross Scripting Framework within the QtScript scripting language |
Kross::EcmaScript | The EcmaScript class implements a Kross::Script to handle a single script |
Kross::ErrorInterface | Interface for error-handling |
Kross::FormDialog | The FormDialog class provides access to KDialog objects as top-level containers |
Kross::FormFileWidget | The FormFileWidget class provides access to a KFileWidget |
Kross::FormModule | The FormModule provides access to UI functionality like dialogs or widgets |
Kross::FormProgressDialog | The FormProgressDialog class provides access to progressbar |
Kross::Interpreter | Base class for interpreter implementations |
Kross::InterpreterInfo | The InterpreterInfo class provides abstract information about a Interpreter before the interpreter-backend itself is loaded |
Kross::InterpreterInfo::Option | Each interpreter is able to define options we could use to manipulate the interpreter behaviour |
Kross::KjsInterpreter | The KjsInterpreter class implements Kross::Interpreter for the KDE Javascript interpreter backend |
Kross::KjsScript | The KjsScript class implements Kross::Script to provide scripts for the KDE JavaScript interpreter backend |
Kross::Manager | The Manager class is a singleton that provides the main entry point to deal with the Kross Scripting Framework |
Kross::MetaFunction | The MetaFunction class implements a QObject to provide an adaptor between Qt signals+slots and scripting functions |
Kross::MetaType | Base class for metatype-implementations |
Kross::MetaTypeImpl< METATYPE > | Metatypes which are registered in the QMetaType system |
Kross::MetaTypeVariant< VARIANTTYPE > | Metatypes which are listened in QVariant::Type |
Kross::MetaTypeVoidStar | Metatype for generic VoidStar pointers |
Kross::Object | The class Object does provide us scripting objects like class instances to the C++ world |
Plugin | |
Kross::Script | Base class for interpreter dependent functionality each script provides |
Kross::ScriptingPlugin | The ScriptingPlugin class loads additional actions stored in rc files with the KrossScripting format, e.g |