Topic: Trying to understand persistance...
Somebody please tell me if I have this right: As a channel plays sequentially loading app after app, each app is reinstantiated each time it is appears. So, if my app opens a socket and gets some XML it has to do that every time it loads... On the other hand, an app that is re-sized is not reinstantiated - just a simple onResize event occurs...
What I'd like to do is to have the user interact with my widget and have the interactive state stored from instantiation to instantiation. The Sony documentation (sorry, I've got a Dash and I know it's "odd") indicates that there is a _root._chumby_widget_state property that can be set and read from instantiation to instantiation. None of the Chumby documentation alludes to this property. Would anyone know if this property exists?
I know that _chumby_set_widget_parameters will allow me to persist over reboots because it is uploaded to the server. But that's not necessary here (might be nice) ...
So, to rephrase, is there a down and dirty way to persist from instantiation to instantiation without hitting the Chumby servers? The only link I can find mentions Flash player's SharedObject class, but there's not much info on that in the Chumby.. Thx wlovin