Skip to content
Snippets Groups Projects
  1. Mar 11, 2019
    • Paul Kaplan's avatar
      Remove some of the high-volume analytics events · e746b98d
      Paul Kaplan authored
      Too much traffic, not enough value. Leaving stuff having to do with tips library/tutorial card navigation as well as hardware extension connectivity, as those help us find issues with Scratch.
      e746b98d
  2. Feb 13, 2019
  3. Feb 11, 2019
  4. Dec 25, 2018
  5. Dec 20, 2018
  6. Dec 18, 2018
  7. Dec 12, 2018
  8. Nov 05, 2018
  9. Oct 18, 2018
    • Ben Wheeler's avatar
      handle many modes of new project creation · b0c4bee8
      Ben Wheeler authored
      responding to canSave without needing canSaveNew prop
      removed canSaveNew
      added default for onUpdateProjectId
      removed conflict files erroneously added
      don't pass down onError
      got tests passing
      better creating and saving logic and names
      b0c4bee8
  10. Oct 17, 2018
  11. Oct 11, 2018
  12. Oct 10, 2018
  13. Oct 08, 2018
  14. Sep 07, 2018
  15. Sep 06, 2018
  16. Jul 20, 2018
  17. Jul 18, 2018
  18. Jun 06, 2018
  19. May 21, 2018
    • chrisgarrity's avatar
      Combine GUI reducers · 44c76e57
      chrisgarrity authored
      * Export initial states for each reducer
      * combine all gui reducers (excludes scratchPaint and intl)
      * combine all initial states to create default guiState for preloading in www
      * expect all of the gui state to be accessible at `state.scratchGui`
      44c76e57
  20. Apr 12, 2018
    • Ray Schamp's avatar
      Rename LoadButton and add docs · ab6f8757
      Ray Schamp authored
      ab6f8757
    • Ray Schamp's avatar
      Add dividers · f1163634
      Ray Schamp authored
      It's a cleaner API IMO but ended up being a messy implementation...
      f1163634
    • Ray Schamp's avatar
      Hook up save and load buttons · cde8a78e
      Ray Schamp authored
      These use a technique where the save/load functionality is passed from the component to its children via a function argument.  I opted for this rather than a higher order component because it is more readable and requires fewer intermediary components.
      
      This could just as easily been done with a higher order component and would be happy to change it to that instead.
      
      There is a performance implication since there is a function being defined in render. However the menu bar is not a highly re-rendered component, so I thought it would be ok in this case.
      cde8a78e
  21. Apr 09, 2018
  22. Mar 23, 2018
Loading