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
While working on #1374, I was examining commits for localeInfoModule.js, the primary source for PhET locale information that is displayed in Preferences and elsewhere.
This is a single commit by @jonathanolson in GitHub for this file, with this message:
Adding ROUGH DRAFT locale switcher for development purposes, see #1302
In both cases the use of cap ("VERY rough-draft" and "ROUGH DRAFT") seems significant. And there's even an acknowledge that this isn't ready for production ("for development purposes") - which I can vouch for given issues like #1374.
So given that a huge amount of work has been done since August to support dynamic locale, and that this is the foundation that's now "included in all sims"... Do you think we should move this from the "ROUGH DRAFT" stage to production-ready?
The "rough draft" parts referred to the temporary locale switcher, which has been phased out and removed. Is there something that should be done about locale info? I'm not aware of any "rough" bits right now.
While working on #1374, I was examining commits for localeInfoModule.js, the primary source for PhET locale information that is displayed in Preferences and elsewhere.
There is a single comment by @jonathanolson about this file in #1302 (comment):
This is a single commit by @jonathanolson in GitHub for this file, with this message:
In both cases the use of cap ("VERY rough-draft" and "ROUGH DRAFT") seems significant. And there's even an acknowledge that this isn't ready for production ("for development purposes") - which I can vouch for given issues like #1374.
So given that a huge amount of work has been done since August to support dynamic locale, and that this is the foundation that's now "included in all sims"... Do you think we should move this from the "ROUGH DRAFT" stage to production-ready?
@jonathanolson for comment. @kathy-phet for prioritization.
The text was updated successfully, but these errors were encountered: