CODAP wrapper: Environment should be save/loadable in CODAP file

[matthew-blackman]

Note: We would also like to save/load the simulation state if possible.

[samreid]

Perhaps the documentation at https://github.com/concord-consortium/codap/wiki/CODAP-Data-Interactive-Plugin-API#interactivestate will help

[samreid]

There is a project at https://github.com/concord-consortium/codap-plugin-api that looks like it provides support for saving/loading the state and configuration. I looked to see if we could adapt its pattern in our existing wrapper, but it was unclear. We could try porting our wrapper to use that plugin-api and see if it helps.

[samreid]

I tried building and adding references to the codap-plugin-api and ran into several problems:

• The built files are *.js but they reference each other without suffixes. I went through and added suffixes
• The iframe-phone uses require but the codap-plugin-api uses import

Could not get things working and I'm not sure whether this is a good idea.

[samreid]

@matthew-blackman and I got this working yesterday. I improved the state handling logic and committed a working version. This should be reviewed and tested, and we will need to know whether to implement this for the tool data wrapper as well.

[matthew-blackman]

@catherinecarter @samreid and I reviewed this and everything is working well in our testing. The save/load, copy and 'shared view' features are all supported by the wrapper. This includes the simulation state, the checkboxes and the CODAP data. Closing.