Getting PhET-iO ready for review for screens 1-3

[AgustinVallejo]

No description provided.

[jbphet]

@AgustinVallejo and I have taken a first shot at this, so screens 1 through 3 are ready for an initial review. I have to admit, I don't feel like I'm very good at deciding what the tree should look like, what should be featured, and where documentation is needed. I suspect this will take several reviews to get it into reasonable shape.

@arouinfar - Please review and let us know what needs to be changed. If it would be more efficient to do this together and potentially make some changes in real time, feel free to set up a meeting.

The dev version phet-io index can be found at https://phet-dev.colorado.edu/html/quantum-measurement/1.0.0-dev.10/phet-io/.

[AgustinVallejo]

After today's meeting with Amy we talked about these improvements:

COINS

• Identical Coins: Include title in the component.
• CoinBias/StateToPrepare: Ensure the title doesn't show when both probability sliders have been hid.

PHOTONS

• polarizationAngleControl: Add some margin to the panel
• Ensure polarization indicator cannot escape (reinforce security measures and double the guards).
• photonTestingArea: Totally uninstrument visibility properties:
  • Exclude visibility of classical/quantum radio buttons.
  • Exclude visibility of the laser button and slider.
• Uninstrument AveragePolarization title.
  Uninstrument individual classical/quantum components. (Based on discussion in RadioButtonGroup PhET-iO API revision sun#920, this is not going to be supported.)
• Link detector nodes and corresponding model elements.

SPIN

• Ensure visibility of button and slider on the laser and uninstrument other visibilities.
• BlochSphere: Don’t hide the sphere itself, only the entire node.
• Manage visibility of measurementDevices as a whole.
• Instrument histograms and include %% data somewhere.

[AgustinVallejo]

Closing as the main things have been done. More PhET-iO discussion in #71

[phet-dev]

Reopening because there is a TODO marked for this issue.

[jbphet]

There have been some refinements made to this and an issue is set up for review, see #79. Closing this one.