[Development] Toolability of mixing QML and JS

Alan Alpert 416365416c at gmail.com
Fri Jun 28 10:03:17 CEST 2013

On Thu, Jun 27, 2013 at 12:43 AM, Alberto Mardegan
<mardy at users.sourceforge.net> wrote:
> On 06/26/2013 08:38 PM, Alan Alpert wrote:
>> I agree. There should be a purely declarative approach for all the
>> "pure UI" parts, and a "triggers" property on State or a
>> StateChangeConnections element would be an improvement.
> What about this?
> onMySignal: PropertyChanges {
>     target: myObject
>     status: "dead"
> }

That's confusing, because onMySignal looks like a signal handler but
behaves like a property (the RHS of a signal handler should be a JS
expression with the return type discarded).

Alan Alpert

More information about the Development mailing list