You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -811,6 +812,17 @@ mindful of the option naming to make sure that you don't cause name collisions.
811
812
Try to keep related options groups together, both for instantiation and `merge` statements. For examples, if you
812
813
have several options related to a11y, keep them together, don't interleave them with other options.
813
814
815
+
### Scenes
816
+
817
+
Author: @jessegreenberg
818
+
819
+
A "Scene" in a PhET simulation is a collection of elements presented to the user. When a new scene is selected,
820
+
elements of the previous scene will be swapped out for elements in the new scene. A single simulation Screen may have
821
+
multiple Scenes. The implementation of a Scene should adhere to the [Model-View-Controller (MVC)](https://github.com/phetsims/phet-info/blob/master/doc/phet-software-design-patterns.md#model-view-controller-mvc)
822
+
pattern and be implemented like any other component in a simulation. There is no base class called Scene which
823
+
combines a SceneModel and a SceneView. Instead, model information for a Scene should exist with the rest of the
824
+
simulation model and view code for a scene should exist with the rest of the simulation view code.
825
+
814
826
### Nesting
815
827
816
828
If using composition for your class, and you want to pass options into a subcomponent, you can nest
0 commit comments