react-split-pane 0.1.87 → 0.1.89

package/CHANGELOG.md

@@ -0,0 +1,21 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
+
+### [0.1.89](https://github.com/tomkp/react-split-pane/compare/v0.1.88...v0.1.89) (2019-11-12)
+
+
+### Bug Fixes
+
+* also include named exports ([bfd16af](https://github.com/tomkp/react-split-pane/commit/bfd16afe8e4f186968ecfd73929a961a9525abed))
+* ignore changelog in prettier ([7c0a6a4](https://github.com/tomkp/react-split-pane/commit/7c0a6a4f123fe266dece1d823bd0de580cca6507))
+
+### [0.1.88](https://github.com/tomkp/react-split-pane/compare/v0.1.87...v0.1.88) (2019-11-12)
+
+### Features
+
+- new less complex site w parcel and gh-pages deploys ([#378](https://github.com/tomkp/react-split-pane/issues/378)) ([ea98d68](https://github.com/tomkp/react-split-pane/commit/ea98d6853f71c479b3b351a4dd23520fe7595409))
+
+### Bug Fixes
+
+- excluded react and react-dom from bundle ([#349](https://github.com/tomkp/react-split-pane/issues/349)) ([eb6b2bc](https://github.com/tomkp/react-split-pane/commit/eb6b2bc92873f1b671243de4f8fba96029f119df))

package/README.md

@@ -7,9 +7,10 @@
 [![Build Status](https://img.shields.io/travis/tomkp/react-split-pane/master.svg?style=flat-square)](https://travis-ci.org/tomkp/react-split-pane)
 [![Coverage Status](https://img.shields.io/coveralls/tomkp/react-split-pane/master.svg?style=flat-square)](https://coveralls.io/r/tomkp/react-split-pane)
 
-Split-Pane React component, can be nested or split vertically or horizontally. Check out some demos [here](http://react-split-pane.surge.sh/)!
+Split-Pane React component, can be nested or split vertically or horizontally!
 
 ## Installing
+
 ```sh
 npm install react-split-pane
 
@@ -19,26 +20,28 @@ yarn add react-split-pane
 ```
 
 ## Example Usage
+
 ```jsx
- <SplitPane split="vertical" minSize={50} defaultSize={100}>
-     <div></div>
-     <div></div>
- </SplitPane>
+<SplitPane split="vertical" minSize={50} defaultSize={100}>
+  <div />
+  <div />
+</SplitPane>
 ```
 
 ```jsx
-  <SplitPane split="vertical" minSize={50}>
-      <div></div>
-      <SplitPane split="horizontal">
-          <div></div>
-          <div></div>
-      </SplitPane>
+<SplitPane split="vertical" minSize={50}>
+  <div />
+  <SplitPane split="horizontal">
+    <div />
+    <div />
   </SplitPane>
+</SplitPane>
 ```
 
 ## Props
 
 ### primary
+
 By dragging 'draggable' surface you can change size of the first pane.
 The first pane keeps then its size while the second pane is resized by browser window.
 By default it is the left pane for 'vertical' SplitPane and the top pane for 'horizontal' SplitPane.
@@ -52,13 +55,14 @@ You can also set the size of the pane using the `size` prop. Note that a size se
 In this example right pane keeps its width 200px while user is resizing browser window.
 
 ```jsx
-    <SplitPane split="vertical" defaultSize={200} primary="second">
-        <div></div>
-        <div></div>
-    </SplitPane>
+<SplitPane split="vertical" defaultSize={200} primary="second">
+  <div />
+  <div />
+</SplitPane>
 ```
 
 ### maxSize
+
 You can limit the maximal size of the 'fixed' pane using the maxSize parameter with a positive value (measured in pixels but state just a number).
 If you wrap the SplitPane into a container component (yes you can, just remember the container has to have the relative or absolute positioning),
 then you'll need to limit the movement of the splitter (resizer) at the end of the SplitPane (otherwise it can be dragged outside the SplitPane
@@ -68,30 +72,34 @@ And more: if you set the maxSize to negative value (e.g. -200), then the splitte
 size of the 'resizable' pane in this case). This can be useful also in the full-screen case of use.
 
 ### step
+
 You can use the step prop to only allow resizing in fixed increments.
 
 ### onDragStarted
+
 This callback is invoked when a drag starts.
 
 ### onDragFinished
+
 This callback is invoked when a drag ends.
 
 ### onChange
+
 This callback is invoked with the current drag during a drag event. It is recommended that it is wrapped in a debounce function.
 
 ### Inline Styles
 
 You can also pass inline styles to the components via props. These are:
 
- * `style` - Styling to be applied to the main container.
- * `paneStyle` - Styling to be applied to both panes
- * `pane1Style` - Styling to be applied to the first pane, with precedence over `paneStyle`
- * `pane2Style` - Styling to be applied to the second pane, with precedence over `paneStyle`
- * `resizerStyle` - Styling to be applied to the resizer bar
+- `style` - Styling to be applied to the main container.
+- `paneStyle` - Styling to be applied to both panes
+- `pane1Style` - Styling to be applied to the first pane, with precedence over `paneStyle`
+- `pane2Style` - Styling to be applied to the second pane, with precedence over `paneStyle`
+- `resizerStyle` - Styling to be applied to the resizer bar
 
 ## Persisting Positions
 
-Each SplitPane accepts an onChange function prop.  Used in conjunction with
+Each SplitPane accepts an onChange function prop. Used in conjunction with
 defaultSize and a persistence layer, you can ensure that your splitter choices
 survive a refresh of your app.
 
@@ -99,89 +107,129 @@ For example, if you are comfortable with the trade-offs of localStorage, you
 could do something like the following:
 
 ```jsx
-    <SplitPane split="vertical" minSize={50}
-               defaultSize={ parseInt(localStorage.getItem('splitPos'), 10) }
-               onChange={ size => localStorage.setItem('splitPos', size) }>
-        <div></div>
-        <div></div>
-    </SplitPane>
+<SplitPane
+  split="vertical"
+  minSize={50}
+  defaultSize={parseInt(localStorage.getItem('splitPos'), 10)}
+  onChange={size => localStorage.setItem('splitPos', size)}
+>
+  <div />
+  <div />
+</SplitPane>
 ```
 
-Disclaimer: localStorage has a variety of performance trade-offs.  Browsers such
+Disclaimer: localStorage has a variety of performance trade-offs. Browsers such
 as Firefox have now optimized localStorage use so that they will asynchronously
 initiate a read of all saved localStorage data for an origin once they know the
-page will load.  If the data has not fully loaded by the time code accesses
+page will load. If the data has not fully loaded by the time code accesses
 localStorage, the code will cause the page's main thread to block until the
-database load completes.  When the main thread is blocked, no other JS code will
-run or layout will occur.  In multiprocess browsers and for users with fast
-disk storage, this will be less of a problem.  You *are* likely to get yelled at
+database load completes. When the main thread is blocked, no other JS code will
+run or layout will occur. In multiprocess browsers and for users with fast
+disk storage, this will be less of a problem. You _are_ likely to get yelled at
 if you use localStorage.
 
 A potentially better idea is to use something like
 https://github.com/mozilla/localForage although hooking it up will be slightly
-more involved.  You are likely to be admired by all for judiciously avoiding
+more involved. You are likely to be admired by all for judiciously avoiding
 use of localStorage.
 
 ## Example styling
 
 This gives a single pixel wide divider, but with a 'grabbable' surface of 11 pixels.
 
-Thanks to ```background-clip: padding-box;``` for making transparent borders possible.
-
+Thanks to `background-clip: padding-box;` for making transparent borders possible.
 
 ```css
+.Resizer {
+  background: #000;
+  opacity: 0.2;
+  z-index: 1;
+  -moz-box-sizing: border-box;
+  -webkit-box-sizing: border-box;
+  box-sizing: border-box;
+  -moz-background-clip: padding;
+  -webkit-background-clip: padding;
+  background-clip: padding-box;
+}
+
+.Resizer:hover {
+  -webkit-transition: all 2s ease;
+  transition: all 2s ease;
+}
+
+.Resizer.horizontal {
+  height: 11px;
+  margin: -5px 0;
+  border-top: 5px solid rgba(255, 255, 255, 0);
+  border-bottom: 5px solid rgba(255, 255, 255, 0);
+  cursor: row-resize;
+  width: 100%;
+}
+
+.Resizer.horizontal:hover {
+  border-top: 5px solid rgba(0, 0, 0, 0.5);
+  border-bottom: 5px solid rgba(0, 0, 0, 0.5);
+}
+
+.Resizer.vertical {
+  width: 11px;
+  margin: 0 -5px;
+  border-left: 5px solid rgba(255, 255, 255, 0);
+  border-right: 5px solid rgba(255, 255, 255, 0);
+  cursor: col-resize;
+}
+
+.Resizer.vertical:hover {
+  border-left: 5px solid rgba(0, 0, 0, 0.5);
+  border-right: 5px solid rgba(0, 0, 0, 0.5);
+}
+.Resizer.disabled {
+  cursor: not-allowed;
+}
+.Resizer.disabled:hover {
+  border-color: transparent;
+}
+```
+
+## New Version
+
+**I'm working on an updated version of this library, and looking for help:**
 
-    .Resizer {
-        background: #000;
-        opacity: .2;
-        z-index: 1;
-        -moz-box-sizing: border-box;
-        -webkit-box-sizing: border-box;
-        box-sizing: border-box;
-        -moz-background-clip: padding;
-        -webkit-background-clip: padding;
-        background-clip: padding-box;
-    }
-
-     .Resizer:hover {
-        -webkit-transition: all 2s ease;
-        transition: all 2s ease;
-    }
-
-     .Resizer.horizontal {
-        height: 11px;
-        margin: -5px 0;
-        border-top: 5px solid rgba(255, 255, 255, 0);
-        border-bottom: 5px solid rgba(255, 255, 255, 0);
-        cursor: row-resize;
-        width: 100%;
-    }
-
-    .Resizer.horizontal:hover {
-        border-top: 5px solid rgba(0, 0, 0, 0.5);
-        border-bottom: 5px solid rgba(0, 0, 0, 0.5);
-    }
-
-    .Resizer.vertical {
-        width: 11px;
-        margin: 0 -5px;
-        border-left: 5px solid rgba(255, 255, 255, 0);
-        border-right: 5px solid rgba(255, 255, 255, 0);
-        cursor: col-resize;
-    }
-
-    .Resizer.vertical:hover {
-        border-left: 5px solid rgba(0, 0, 0, 0.5);
-        border-right: 5px solid rgba(0, 0, 0, 0.5);
-    }
-    .Resizer.disabled {
-      cursor: not-allowed;
-    }
-    .Resizer.disabled:hover {
-      border-color: transparent;
-    }
-
- ```
+Demo
+
+http://react-split-pane-v2.surge.sh/
+
+Install
+
+```sh
+npm install react-split-pane@next
+
+# or if you use yarn
+
+yarn add react-split-pane@next
+```
+
+Usage
+
+```jsx
+import SplitPane, { Pane } from 'react-split-pane';
+
+<SplitPane split="vertical">
+  <Pane initialSize="200px">You can use a Pane component</Pane>
+  <div>or you can use a plain old div</div>
+  <Pane initialSize="25%" minSize="10%" maxSize="500px">
+    Using a Pane allows you to specify any constraints directly
+  </Pane>
+</SplitPane>;
+```
+
+Pull request
+
+https://github.com/tomkp/react-split-pane/pull/240
+
+More discussion
+
+https://github.com/tomkp/react-split-pane/issues/233
 
 ## Contributing
 
@@ -189,6 +237,4 @@ I'm always happy to receive Pull Requests for contributions of any kind.
 
 Please include tests and/or update the examples if possible.
 
-**I'm working on an updated version of this library, and looking for help:** https://github.com/tomkp/react-split-pane/pull/240
-
-Thanks, Tom  
+Thanks, Tom