Re: [Development] Toolability of mixing QML and JS

2013-06-26 Thread Shawn Rutledge
On 26 June 2013 19:38, Alan Alpert <4163654...@gmail.com> wrote: > Obviously a complete declarative API is a work in progress. But as a > first step we should consider a "trigger" property on State which you > can set to a signal (e.g. mousearea.clicked) so as to handle that case > declaratively.

Re: [Development] Toolability of mixing QML and JS

2013-06-26 Thread Bubke Marco
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

Re: [Development] Toolability of mixing QML and JS

2013-06-26 Thread Bubke Marco
Sorry for the formatting but the web email client is improvable. Rutledge Shawn: I see it as an issue if you had to write that parser. No wonder it's out of sync with the actual language parser. The one in declarative should have all the features that you need, with suitable (ideally even publi