{"push_id":809110036,"size":14,"distinct_size":4,"ref":"refs/heads/addSlidersToNodes","head":"3b7a20913562bf95b01f1c9019ecb3a93c2712b9","before":"0faef750ff57a751a4a9adf1103cf660866665db","commits":[{"sha":"f914fe870106ae1f111b86ecf7707e7d96a898ab","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Add initial version of extended Simulation Panel\n\nThe only button that does anything currently is the Run button\n\n[#102292942]","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/f914fe870106ae1f111b86ecf7707e7d96a898ab"},{"sha":"7b4f7ca63ef9bf32a5fa76e8fd7535efd521e334","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Replace DocumentAction buttons with new icons","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/7b4f7ca63ef9bf32a5fa76e8fd7535efd521e334"},{"sha":"b9e9411a693e871501a4b0c48d4627abfcf0fe71","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Replace input sliders with ValueSlider\n\n[#102292942]","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/b9e9411a693e871501a4b0c48d4627abfcf0fe71"},{"sha":"3ebd7c64cfe6aacb2afbe3006eb7fc02cf8f13b8","author":{"email":"3f8753993a1e1fe9185f213c3280a239503810cd@gmail.com","name":"Noah Paessel"},"message":"Merge pull request #91 from concord-consortium/simulation-panel\n\nSimulation panel","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/3ebd7c64cfe6aacb2afbe3006eb7fc02cf8f13b8"},{"sha":"22eebbbd5a8154608ef9ad15419668b53c4097c5","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Move runSimulation and graphIsValid to SimulationStore\n\nThis is anticipating a greater connection between the store and the\nsimulation panel, which will be needed once we start setting the\nnumber of steps etc.\n\n[#102292942]","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/22eebbbd5a8154608ef9ad15419668b53c4097c5"},{"sha":"073d9cc34144dc4a6b8146071dd00b6d851a6406","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Add graphIsValid state to run button","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/073d9cc34144dc4a6b8146071dd00b6d851a6406"},{"sha":"9da6523f8d0575fa5bd85bf903b1043732edde07","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Remove value from Slider's state\n\nThis makes it more like a controlled component, such as `<input>`\n(see [1](https://facebook.github.io/react/docs/forms.html#controlled-components)\nand [2](http://leftdevel.com/blog/reactjs-controlled-forms/))\n\nBy not duplicating \"value\" in state, we have just one source of truth,\nand remove any confusion of whether we're talking about the state or\nthe property at any point.\n\nWith a controlled component, we need to have some other variable owned\nby the parent that gets updated, and then re-renders the slider component\nwith the new value. This seems like extra overhead, but in practice we'll\nalways want the slider to be attached to some property anyway. Updated\ndemo to reflect this.\n\nUnfortunately, in this case it's not *exactly* the same as a React\n`<input>` component, because the slider will actually move when you\ndrag it, even if you haven't hooked up the listener. This is because\nthe position of the handle when dragged is being set by jQuery, not the\nvalue of `value`. But I think that's a minor concern.\n\nAlso change \"min-height\" to `minHeight` to remove one warning from JS console.","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/9da6523f8d0575fa5bd85bf903b1043732edde07"},{"sha":"98521d7e24084e5ed6ac14d7cddb863b10be689b","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Make Slider min and max editable\n\nLike `value`, min and max are controlled properties, and so a parent\nneeds to set min and max based on an onRangeChanged event.\n\nValues are checked for sanity after user clicks away or hits return.\n\nMost of this code from node-value-inspector-view, which will eventually\nbe replaced by this view.\n\nUpdate slider demo.\n\n[#102292942]","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/98521d7e24084e5ed6ac14d7cddb863b10be689b"},{"sha":"d186c4ef85e0d3a95e2189f5b9fd8ca7395b10d5","author":{"email":"d65828e0e5d3a7da1eeff236b882ad657281440d@concord.org","name":"Sam Fentress"},"message":"Use editable slider range to set simulation steps\n\nAlso set max steps to 5000\n\n[#102292942][#102606120]","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/d186c4ef85e0d3a95e2189f5b9fd8ca7395b10d5"},{"sha":"7715fe4ef2c61fa7a6f7ff7095bf8a9286955acb","author":{"email":"3f8753993a1e1fe9185f213c3280a239503810cd@gmail.com","name":"Noah Paessel"},"message":"Merge pull request #92 from concord-consortium/simulation-editable-steps\n\nSimulation editable steps","distinct":false,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/7715fe4ef2c61fa7a6f7ff7095bf8a9286955acb"},{"sha":"f83d321049cac3ed3ed50f94545f12482d162902","author":{"email":"3f8753993a1e1fe9185f213c3280a239503810cd@gmail.com","name":"Noah Paessel"},"message":"Initial effort: Adding value slider to Nodes.  [#102293636]\n\nhttps://www.pivotaltracker.com/story/show/102293636","distinct":true,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/f83d321049cac3ed3ed50f94545f12482d162902"},{"sha":"898912c2804f61c98f8dc53a99b6fdeb24c1240d","author":{"email":"3f8753993a1e1fe9185f213c3280a239503810cd@gmail.com","name":"Noah Paessel"},"message":"Add type faces. Remove unused new-icons.css","distinct":true,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/898912c2804f61c98f8dc53a99b6fdeb24c1240d"},{"sha":"d9019f5f1b8feeffd064ee7242ef729047d44f65","author":{"email":"3f8753993a1e1fe9185f213c3280a239503810cd@gmail.com","name":"Noah Paessel"},"message":"Restyle Nodes. Closer to the PSDs.","distinct":true,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/d9019f5f1b8feeffd064ee7242ef729047d44f65"},{"sha":"3b7a20913562bf95b01f1c9019ecb3a93c2712b9","author":{"email":"3f8753993a1e1fe9185f213c3280a239503810cd@gmail.com","name":"Noah Paessel"},"message":"Get `is_simulating` props from the SimulationStore","distinct":true,"url":"https://api.github.com/repos/concord-consortium/building-models/commits/3b7a20913562bf95b01f1c9019ecb3a93c2712b9"}]}