W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2013

Re: On <scxml> not being a <state>

From: Gavin Kistner <phrogz@me.com>
Date: Tue, 19 Feb 2013 20:46:53 -0700
Cc: "www-voice@w3.org" <www-voice@w3.org>
Message-id: <0871C057-4757-4EC8-B7C3-019F150B88F1@me.com>
To: Jim Barnett <Jim.Barnett@genesyslab.com>
On Feb 19, 2013, at 4:28 PM, Jim Barnett <Jim.Barnett@genesyslab.com> wrote:
> “The Platform _must_ provide a way for the environment to specify the initial state configuration and state of the datamodel.   Such a specification _must_ take precedence over the value of <scxml>’s initial attribute”

FWIW it is important for my application to ensure that the states are actually entered (and not just teleported into the configuration) because I rely on certain callback events exposed by the interpreter as states are entered/exited. 

> For the time being, though, since you need a specified location to re-write, why not use <scxml>’s ‘intial’ attribute?  It can take multiple values, so it should work just as well as history.

I need to not immediately boot into the restored state. I need to be in a "splash screen" state while certain boot-up procedures happen. Only once all is ready does my application inject a system.initialized event into the system, and then one of multiple transitions responding to that event _might_ cause the state to be restored (depending on which conditional transition is taken). 

> Neither ‘initial’ nor <history> will restore the previous values of the datamodel, though.  That’s why I thought something like <anchor>, which snapshots the datamodel, might be of interest. 

A good point to keep in mind. In my case most of the application data is stored outside the state machine data model, and this data (and the data model) are both restored appropriately during startup.
Received on Wednesday, 20 February 2013 03:47:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 20 February 2013 03:47:27 GMT