| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | We cant rely on property attributes from JavaScriptCore for the setter and ↵ | Olivier Goffart | 2009-07-16 | 1 | -3/+3 | |
| | | | | | getter | |||||
| * | Convert the strings or number value to jscvalue when they are used with an ↵ | Olivier Goffart | 2009-07-16 | 1 | -12/+14 | |
| | | | | | | | | engine Also change the stringValue not to be a pointer. This fixes a memory leak. | |||||
| * | don't try to be so clever | Kent Hansen | 2009-07-15 | 1 | -7/+4 | |
| | | | | | | | If we implement the ability to change the global object, the global object pointer can change, so we need to keep a reference to the object if it's stored in a QScriptValue. | |||||
| * | implement ability to dynamically change class of script objects | Kent Hansen | 2009-07-10 | 1 | -25/+52 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. | |||||
| * | use JSC::call() and JSC::construct() | Kent Hansen | 2009-07-09 | 1 | -54/+2 | |
| | | ||||||
| * | Fix autotest checking QScriptValue::objectId method. | Jedrzej Nowacki | 2009-07-09 | 1 | -7/+2 | |
| | | | | | (QScriptValue::objectId() and QScriptEnigne::objectById) | |||||
| * | use currentFrame instead of globalExec whenever we can | Kent Hansen | 2009-07-09 | 1 | -27/+27 | |
| | | ||||||
| * | support callees that are not function objects | Kent Hansen | 2009-07-09 | 1 | -4/+4 | |
| | | | | | E.g. QScriptClass-based objects. | |||||
| * | rewrite most of QScriptContext handling | Kent Hansen | 2009-07-08 | 1 | -5/+90 | |
| | | | | | Do it The right way(TM), by lazily wrapping JSC::ExecState objects. | |||||
| * | Fix engineDelete autotest. | Jedrzej Nowacki | 2009-07-08 | 1 | -2/+27 | |
| | | ||||||
| * | work on QScriptEngine::uncaughtException() | Kent Hansen | 2009-07-07 | 1 | -2/+10 | |
| | | | | | | | It's possible that JSC evaluate() returns a completion of type Throw without hadException() being true, so we need to store the exception value explicitly. | |||||
| * | fix QScriptValue::construct() when argument is not array-like | Kent Hansen | 2009-07-06 | 1 | -4/+2 | |
| | | ||||||
| * | make QScriptClass::HasInstance extension work | Kent Hansen | 2009-07-06 | 1 | -1/+1 | |
| | | ||||||
| * | make more tests pass | Kent Hansen | 2009-07-03 | 1 | -4/+0 | |
| | | ||||||
| * | implement a fair amount of the QScriptClass functionality | Kent Hansen | 2009-07-02 | 1 | -7/+15 | |
| | | | | | | Enumeration is missing, as is the ability to change the class of an object after it has been created. | |||||
| * | implement QScriptValue::QObjectMember property flag | Kent Hansen | 2009-07-02 | 1 | -0/+2 | |
| | | ||||||
| * | use the JSC::Getter and JSC::Setter flags | Kent Hansen | 2009-07-02 | 1 | -4/+2 | |
| | | ||||||
| * | implement QScriptValue::isQMetaObject() and QScriptValue::toQMetaObject() | Kent Hansen | 2009-06-26 | 1 | -10/+8 | |
| | | ||||||
| * | implement QMetaObject bindings | Kent Hansen | 2009-06-26 | 1 | -2/+2 | |
| | | ||||||
| * | work on signal bindings (connect, disconnect, signal emission) | Kent Hansen | 2009-06-24 | 1 | -3/+3 | |
| | | ||||||
| * | make more qscriptengine tests run | Kent Hansen | 2009-06-24 | 1 | -4/+10 | |
| | | | | | | Not everything passes but at least nothing asserts anymore, so the test runs to completion. | |||||
| * | make most of the qscriptvalue tests pass | Kent Hansen | 2009-06-23 | 1 | -69/+138 | |
| | | | | | call(), construct() etc. | |||||
| * | use JSC::asObject() | Kent Hansen | 2009-06-23 | 1 | -40/+36 | |
| | | ||||||
| * | Import JSC-based Qt Script from Kent's tree. | Simon Hausmann | 2009-06-16 | 1 | -0/+2303 | |
 |
index : Qt.git | |
| Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed. |
| summaryrefslogtreecommitdiffstats |