-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
phetioFeatured
defaults for Preferences
#875
Comments
I made preferences tabs and their visibleProperties phetioFeatured: true in the commit. The preferencesModel is overwhelming, especially for sims that do not leverage all those features. It seems best to start with that subset being phetioFeatured for the next few releases.
I'll mark it as phetioFeatured: false in the next commit. |
Thanks @samreid. Master generally looks good, but I think you may have accidentally unfeatred |
Thanks, I added that. Can you please test on phet-dev? |
Thanks @samreid, looks good! |
In phetsims/molecule-shapes#230 and phetsims/gravity-and-orbits#470, QA reported that
preferencesDialog.preferencesTabs.LocalizationTab.visibleProperty
was missing from the tree. It's not actually missing, but I realized that it wasn'tphetioFeatured: true
. It seems reasonable to feature anyphetioID
mentioned in the Preferences section PhET-iO Guide, so I reviewed the tree to see what else should be featured.The guide describes how to hide the preferences tabs in the dialog, so I think we should feature
preferencesDialogCapsule.archetype.preferencesTabs.*Tab.visibleProperty
.I also found this in the guide:
The only elements linked under the
preferencesModel
that we specifically refer to in the documentation are the stateful properties:audioEnabledProperty
,localeProperty
, andcolorProfileProperty
. These are allphetioFeatured: true
. However, the quote above suggests that users may want to inspect all of thepreferencesModel
contents, which they can only do if viewing "All" elements. Here's whatpreferencesModel
looks like when viewing Featured vs. All elements.Should we feature all of the target elements collected here? Or should we specify that users should view "All" elements when inspecting the
preferencesModel
? If we only want to feature the stateful properties, thenvoicingEnabledProperty
should bephetioFeatured: false
.For the foreseeable future, most of the properties under
preferencesModel
aren't actually applicable to most sims, so I am leaning towards just featuring the stateful properties. @zepumph @samreid what would you advise?The text was updated successfully, but these errors were encountered: