summaryrefslogtreecommitdiffstats
path: root/src/script/bridge/bridge.pri
Commit message (Collapse)AuthorAgeFilesLines
* Add QScriptDeclarativeClassAaron Kennedy2009-11-101-2/+6
| | | | | | | | | QScriptDeclarativeClass is a private, but exported, class used by the declarativeui module. It is very similar to QScriptClass, but slightly faster and provides a couple of "backdoor" extension mechanisms used by declarative. Reviewed-by: Warwick Allison
* move Global Object to its own fileKent Hansen2009-08-041-0/+2
|
* Move QScriptActivationObject to his own fileOlivier Goffart2009-07-301-2/+4
|
* implement ability to dynamically change class of script objectsKent Hansen2009-07-101-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | With an object created by QScriptEngine::newObject(), it should be possible to call QScriptValue::setClass() to dynamically change the behavior of that object. Similarly, it should be possible to promote plain script objects to QObject (QVariant) wrappers by calling the overload of QScriptEngine::newQObject() (newVariant()) that takes a script object as the first argument. This commit implements this capability. The premise is the (internal) QScriptObject class, which inherits JSC::JSObject. It reimplements all the methods for getting/setting properties etc. Then there's a level of indirection to facilitate dynamic change of the class: Each QScriptObject can have a delegate associated with it that will handle operations on the object. By default there is no delegate, so the object behaves as a normal JS object, as you expect. However, once a delegate is set (e.g., when QScriptValue::setScriptClass() is called), QScriptObject will give the delegate the chance to handle the object operation. In addition to a delegate implementation for QScriptClass-based objects, there are also delegates for QObject and QVariant wrappers. These replace the QObjectWrapperObject and QVariantWrapperObject classes.
* Import JSC-based Qt Script from Kent's tree.Simon Hausmann2009-06-161-0/+9