[Development] Toolability of mixing QML and JS

[Rutledge Shawn]

On 26 Jun 2013, at 12:00 PM, Thomas Hartmann wrote:

> What hurts us more is real imperative code. For example setting a state 
> usually looks like this:
> 
> onSomething {
>    root.state = "someState";
> }
> 
> And it currently has to look like this. There is no real pure 
> declarative way.

Isn't that what "when" is for?

states: [
    State {
        name: "someState"
        when: mousearea.pressed
…

but that's a property change whereas you are talking about connecting to a signal I suppose?  But a property change is notified by means of a signal anyway.