Closed jessegreenberg closed 11 months ago
I think it is an aspirational feature @jessegreenberg. As I understand it, the grant requirements are for character set localization, and we've met that goal.
We can defer this to the next release which will include dynamic locale and unification with/redeployment of the Basics version.
@amanda-phet would we like to include this type of work when adding new character sets? I don't believe it would be difficult to add query parameter support for choosing a character set in all the sims we are hitting.
I went ahead and did this. It's now ready to test and review.
Before we do this. I recommend factoring it out using the same strategy as other features phet has. @marlitas and I talked about first adding it as a package.json phetFeatures
. Then a general query parameter that allows for a graceful default that sims can use to opt into for support. I'd also like to move this issue to joist/
if that's ok.
Some thoughts on work to do:
regionAndCulture
in simFeature.Questions:
Thanks all!
public:true
. Is that right @amanda-phet?options.localizationOptions.queryParameterValue
since that was the strategy to support sim-specific query parameters.After the above commit, ?regionAndCulture
is a query parameter available by every sim. The default is null (empty string), so in all sims you can provide http://localhost:8080/friction/friction_en.html?brand=phet&ea&debugger®ionAndCulture=&locales=*
and it runs successfully. That is a bit awkward but fine. Valid values are set by simFeatures
and validated by a main supported list in RegionAndCulturePortrayal.
There is still some cleanup to do, especially in PreferencesModel. But we are on our way!
Up next in my book:
?regionAndCulture
, using simFeatures.supportedRegionsAndCultureslocalizationOptions.queryParameterValue
because you can just inline the chipper query parameter where needed.[x] I wrote 4 TODOs pointing to this issue, mostly as questions and next steps.
@marlitas let me know if you want to discuss anything more here. I'd be happy to pair again if desired.
I addressed all of the up next checkboxes. Over to @zepumph to review.
Oops, back to me real quick to clean up some QueryParameter files.
That was done in the above commits. Back to @zepumph
In (4), can you please specify the sim or sims that you should use as an example for your new case? https://github.com/phetsims/joist/commit/1d08d5d88be48a3a92f9b7069ffab5e7e38d76cc.
Looks great from a dev perspective. Thanks so much. I'm ready to close, but I'm unsure how much you want to check in and confirm with a designer before closing. Back to you.
Added some sim examples to that documentation. I think this is ready to close.
I heard mention of this in the team meeting today. That is not currently supported, is this a required feature @arouinfar?