- Oct 13, 2016
-
-
Ray Schamp authored
Once another project uses this package, these should become peerDependencies. Until then install automatically.
-
Ray Schamp authored
While doing so: - Use ProjectLoader for loading projects - Stop using loadEmptyProject and supply empty project data - Move project loading to App, GUI now receives data (as a string - the vm should receive an object eventually) - Add logging
-
- Sep 28, 2016
-
-
Ray Schamp authored
-
Ray Schamp authored
-
Ray Schamp authored
-
- Sep 27, 2016
-
-
Ray Schamp authored
-
Ray Schamp authored
-
- Sep 26, 2016
-
-
Ray Schamp authored
Because these are peer dependencies, we should be lenient about the required version of React required to use the components. I didn't use the caret because the x's work and it's obvious what they mean, unlike ^ and ~.
-
Ray Schamp authored
-
- Sep 25, 2016
-
-
Ray Schamp authored
Now they don't have to be built and rebuilt every npm install
-
- Sep 23, 2016
-
-
Ray Schamp authored
-
- Sep 19, 2016
-
-
Ray Schamp authored
Multiple installations of React can cause issues if the package is used just for the components.
-
- Sep 16, 2016
-
-
Ray Schamp authored
-
- Sep 15, 2016
-
-
Ray Schamp authored
-
Ray Schamp authored
-
Ray Schamp authored
Add skeleton toolbox component
-
Ray Schamp authored
-