- Aug 02, 2017
-
-
Paul Kaplan authored
-
- Aug 01, 2017
-
-
Paul Kaplan authored
-
- Jul 27, 2017
-
-
Paul Kaplan authored
-
Ken authored
Changed color and background-color as requested; temporarily hidden the icon
-
- Jul 26, 2017
-
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Ken authored
the background was white and the font color was too - I changed it to be black instead
-
- Jul 21, 2017
-
-
chrisgarrity authored
move all locale data (react-intl/locale-data and gui messages) into locale.js. This also makes switching to an external node package easier because the package just needs to export the same thing as locale.js.
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
- Jul 19, 2017
-
-
chrisgarrity authored
Dynamic import didn’t do what we wanted, so just added `npm run i18n:msgs` to the start command. This is just temporary. Other changes as requested: * exports in one place * loc=> locale Also fixed use of require for localeData to use dynamic import (this one works), so the babelrc changes are needed, otherwise import as a function is not recognized.
-
chrisgarrity authored
Added language-selector component and container. Replaced lib/intl.jsx with reducers/intl.js and added updateIntl to handle language changes. Moved languages.json into src
-
- Jul 14, 2017
-
-
chrisgarrity authored
Keep localization in the container level. Ideally we should not be passing message descriptors.
-
- Jul 10, 2017
-
-
Andrew Sliwinski authored
-
Paul Kaplan authored
-
Andrew Sliwinski authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
- Jul 07, 2017
-
-
Paul Kaplan authored
-
- Jul 06, 2017
-
-
Paul Kaplan authored
-
Paul Kaplan authored
-
- Jun 30, 2017
-
-
Paul Kaplan authored
-
chrisgarrity authored
Costumes and Sound tab strings.
-
- Jun 29, 2017
-
-
Nicolas Terray authored
In order to comply to WCAG 2.0[1], buttons must have discernible text that clearly describe the purpose, so that it can be used by screen readers. [1] https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H65
-
- Jun 27, 2017
-
-
Paul Kaplan authored
-
Paul Kaplan authored
-
Paul Kaplan authored
-
- Jun 23, 2017
-
-
Paul Kaplan authored
-