We need to explicitly formalize how properties to objects and script work

[blairmacintyre]

In the editor views, when you change a property to a script or to an object, it gets "sent to all other editors." That's great when editing/debugging.

When I'm running in the or the Immersive ImmersivePlayer, should changes in the various editors be reflected? If not, why do we keep reading things from the SceneGraph (e.g., to create properties)?

This becomes more complicated if we want to let the scripts change the properties of objects. Should the script change the runtime value, or the script sheet? My intuition says "the runtime values". If a script is moving an object, we absolutely do not want to be sending tons of per frame data.

But what about editing? It would be great to be able to tweet a running experience.

I think we can get a good solution this way:

• at startup, we read all the property values, and set the properties object in the scriptmanager facade.
• all scripts that want to see another object's values read/write from that properties dictionary
• if we want to support real time changes from the editor, any incoming change overrights THAT property in the properties object