[Development] Toolability of mixing QML and JS

Bubke Marco Marco.Bubke at digia.com
Wed Jun 26 16:08:44 CEST 2013

Rutledge Shawn:
On 26 Jun 2013, at 3:00 PM, Bubke Marco wrote:
> The approach with the different process has additional advantage that a crash is not that bad, we can link with different Qt versions and can restart the process because there was a problem which we call "componentComplete lazy programming".

Can you describe more of what goes wrong? I've run into problems with what componentComplete actually means several times too.
componentComplete is called only one time after the component creation. This is fine for the viewer because Qml is designed that its tree is only build one time. For the editor it's a big problem because we change this tree all the time.
We had the idee, that the signal at component creation time will compressed and executed at the end of the component
creation. So the performance use case for componentComplete would be gone.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130626/ca012d0e/attachment.html>

More information about the Development mailing list