Hi,
Some notes from day 4.

- Peter and Zoltan got the green light to sign Google's contributor's 
agreement

- Kent booked recurring voice conference for the weekly status updates; 
first call is on Tuesday next week @ 3pm Oslo time

- Discussion regarding when/if we should switch to "QML2" repository as 
the basis of QtScript/V8
   - We don't know if it contains changes in the way QtScript is used
   - Our problem to solve seems to be the same, though: Handling binding 
expressions that the QML evaluator can't
   - Conclusion: We should switch at some point, but it doesn't seem 
very important right now

- Zoltan submitted his first merge request for the qt-script-ng 
repository: Using v8::ScriptData::PreCompile() to implement QScriptProgram
   - http://qt.gitorious.org/+qt-developers/qt/qt-script-ng/merge_requests
   - Jedrzej, Olivier, Gabriel, Caio and Kent have "reviewer" status on 
the project and can process incoming requests
     - Use the devtools/shell/git-review script

- Olivier found out why one of the qdeclarativeecmascript tests asserts
   - Native property accessors expect access to the scope chain of the 
JS function in which they are called, which we don't support with V8
   - This also lead to the discovery of a bug in 
QScriptContext::pushContext() 
(http://bugreports.qt.nokia.com/browse/QTBUG-18188)
   - QtDeclarative introduced a new API 
(QScriptDeclarativeClass::pushCleanContext()) that works around the bug, 
instead of fixing it
   - Caio writing tests to verify behavior (also on QtScript classic (4.5))

- Final final final build fixes ;-)

- Something I forgot from the previous day: Simon suggested we try to 
reserve new test devices for Peter and Zoltan [Kent to talk to Benedikte]

Kent
_______________________________________________
Qt-script mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-script

Reply via email to