- Sep 24, 2018
-
-
Evelyn Eastmond authored
-
Benjamin Wheeler authored
* added account navigation menu, copied and adapted from www * fixed css * support for login menu, registration menu from www * Dropdown replaced with MenuBarMenu, override www css in menus * render and style login dropdown via function from www * moved menu styling from menu itself to menu bar * refactoring menu components and containers * refactor and restyle account nav menu * cleaned up cruft and css per rschamp's review of PR 3070
-
- Sep 20, 2018
-
-
Evelyn Eastmond authored
-
- Sep 19, 2018
-
-
DD Liu authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
Evelyn Eastmond authored
-
- Sep 18, 2018
-
-
chrisgarrity authored
I left the ability to ignore languages in place so that we can continue to have languages that are available, but not in the menu for everyone.
-
Ray Schamp authored
Follow up on #2464, fix the hacky accessors into the vm and renderer internals.
-
chrisgarrity authored
-
chrisgarrity authored
-
chrisgarrity authored
-
chrisgarrity authored
-
- Sep 17, 2018
-
-
Karishma Chadha authored
-
chrisgarrity authored
* convert all tags to have a `tag` field corresponding to the query parameter, and `intlLabel` field that defines the title message for `FormattedMessage` * define all the tag messages in a shared file so they can be included in multiple places. * convert the `TagButton` to use `tag` for the `onclick` handler value, and localize `intlLabel` for the title. In the library I’ve continued to use `tag.toLowercase()` even though all the tags are currently defined as lowercase. It’s safer, but currently not strictly needed.
-
- Sep 16, 2018
-
-
chrisgarrity authored
Questions: * should the message strings include the number? Or should that get added to the name when the name is defined * added a new ‘shared-messages’ to handle the definition of backdrop, costume, etc which are used in multiple places, they’re all related to defaults, so should it all be in `lib/default-project`
-
- Sep 14, 2018
-
-
chrisgarrity authored
-
- Sep 13, 2018
-
-
chrisgarrity authored
-
- Sep 12, 2018
-
-
Christopher Willis-Ford authored
-
Andrew Sliwinski authored
-
Linda authored
-
Linda authored
-
- Sep 11, 2018
-
-
Linda authored
-
Eric Rosenbaum authored
-
Linda authored
-
- Sep 07, 2018
-
-
Ben Wheeler authored
-
Christopher Willis-Ford authored
-
Evelyn Eastmond authored
-