search

phetsims / rosetta

PhET's Simulation Translation Utility
MIT License
3 stars 1 forks source link

inform user about which sims depend on the sim being translated? #66

Open pixelzoom opened 9 years ago

pixelzoom commented 9 years ago

This problem goes in 2 direction. In https://github.com/phetsims/rosetta/issues/63, I described the case where a sim gets all of its sims from some other sim (e.g. Concentration is a subset of Beer's Law Lab). In that case, you want the user to know that changing Concentration will affect Beer's Law Lab (and any other sims that may get its strings from beers-law-lab!)

The problem goes in the other direction too. If we were translating Beer's Law Lab, changes to its translation will affect Concentration. Does the user need to be aware of that? And how do we determine that dependency? (There's nothing in beers-law-lab that indicates the dependency in that direction.)

pixelzoom commented 9 years ago

Here's another real-world example, the suite of "faraday" sims that may someday be ported from Java. There is one main sim, "Faraday's Electromagnetic Lab", that contains 4 screens. Then there are 3 other sims that are various subsets of screens: "Generator", "Magnet & Compass", "Magnets & Electromagnets". When I translate any 1 of these, I am potentially affecting the other 3. How is the user made aware of that?

jbphet commented 9 years ago

I think that this would be a good design question to address in the second version of the translation utility. The first version, which is coming up on its first round of testing by external translators, was intended to be "bare bones".

I'll mark this issue for discussion at the next developer meeting and we can decide if the rest of the team agrees.

pixelzoom commented 9 years ago

Agreed that this can be addressed in a later version. But I think putting strings from other sims under the "Sim Strings" heading in this first beta is a mistake. See https://github.com/phetsims/rosetta/issues/63#issuecomment-137170522.

jbphet commented 9 years ago

See https://github.com/phetsims/rosetta/issues/63#issuecomment-137538586 for decision on what to do about this in the short term.

aaronsamuel137 commented 9 years ago

Unassigning for now. This will not be addressed in 1.0.

jbphet commented 6 years ago

@ariel-phet - any opinion as to whether this should be addressed as part of chipper:2.0? While it would be an improvement, I don't think that it has been much of an issue for translators, so I'm not very inclined to put this on the list.

ariel-phet commented 6 years ago

@jbphet yes I would continue to punt for the moment, bigger issues for chipper 2.0