swift/objective-C>> react-dip>> 返回
项目作者： mdugue

项目描述 ：
Animated react transitions 💫
高级语言： JavaScript
项目地址: git://github.com/mdugue/react-dip.git
创建时间： 2018-03-22T08:02:10Z
项目社区：https://github.com/mdugue/react-dip
开源协议：MIT License
下载


react-dip

Simple & declarative transition animations for React.

DISCLAIMER

THIS IS EARLY WORK IN PROGRESS AND NOT “RELEASED TO PUBLIC” YET, THOUGH THIS SHOULD HAPPEN ANYTIME SOON.

FEEL FREE TO WATCH 👓, STAR ⭐ OR CONTACT ME TO BE NOTIFIED ABOUT PROGRESS.

TODO: Video / gif here

Version
Size
Size
Greenkeeper badge

CodeFactor
BCH compliance
Known Vulnerabilities
Build Status

Why?

Ever wanted to implement one of those incredible designs you find on dribble or Muzli where one element beautifully transforms into another upon page transition? And then realized “But I want my code to stay statefull, decoupled, scalable, declarative”, so you ended up with regular “hard cuts” instead? – To me this happend very very often!

react-dip solves this by providing animated transisions in an effortless way, that just worksTM, by using the FLIP technique.

Table of contents

Installation

Using yarn or npm:

  1. $ yarn add react-dip
  3. # or using npm
  4. $ npm install --save react-dip

Using a module bundler like webpack or parcel, import your depency just as any other:

  1. // Using ES6 modules
  2. import Dip from 'react-dip'
  4. // or using CommonJS modules
  5. var Dip = require('react-dip')

UMD builds are also available via unpkg:

  1. <script src="https://unpkg.com/react-dip/dist/react-dip.umd.min.js" ></script>

Quick Start

The API is as small as possible, almost everything is optional, so you see results immediately. Just wrap your Items in a Dip

  1. import React, {Component} from 'react'
  2. import Dip from 'react-dip'
  4. function Component1() {
  5.   return (
  6.     <Dip dipId="quickStart" style={{background: 'red'}}>
  7.       some content
  8.     </Dip>
  9.   )
  10. }
  12. function Component2() {
  13.   return (
  14.     <Dip
  15.       dipId="quickStart"
  16.       style={{position: 'absolute', top: '100px', background: 'green'}}
  17.     >
  18.       some other content <br />
  19.       etc...
  20.     </Dip>
  21.   )
  22. }
  24. // use complex state here
  25. // or a routing solution such as react-router
  26. // or connect it to redux, or ustated
  27. export default class MyStatefulParent extends Component {
  28.   state = {currentStep: 0}
  29.   toggleState = () =>
  30.     this.setState(state => ({
  31.       currentStep: (state.currentStep + 1) % 2,
  32.     }))
  33.   render() {
  34.     return (
  35.       <section>
  36.         <h1> Quick Start example </h1>
  37.         <button onClick={this.toggleState}>toggle me</button>
  38.         {this.state.currentStep === 0 ? <Component1 ></Component1> : <Component2 ></Component2>}
  39.       </section>
  40.     )
  41.   }
  42. }

Note: Using inline styles as well as absolute positioning is usually not considered a good way and is applied here for the sake of simplicity.
You can use any type CSS or CSS-in-JS styling and fluid / flex / grid layout.

Edit react-dip Quick Start

Props

The API surface is intetended to be as simple as possible. Only dipId and children (or render) are required props. The rest is optional and helps you fine tuning your animations.

dipId

string | Required!

The id that groups two different dip elements. React-dip will only create animated transitions between to Elements with the same dipId, consider them as potential from- and to-hints.

children

React Element | Required unless using render-prop!

Content that is rendered as part of that Dip.

render

function({ref: function(), styles: {}}) | Required unless using children-prop!

Function that should return the content that is rendered as part of that Dip. Allows for more advanced pattern and skips the wrapping Element. See render prop for further details.

Warning: <Dip render> takes precedence over <Dip children> so don’t use both in the same <Dip ></Dip>.

duration

number | optional, defaults to 200

Time in milliseconds the animation will take when transitioning to this dip.

easing

string | optional, defaults to "ease-out"

Specifies the desired timing function. Accepts the pre-defined values linear, ease, ease-in, ease-out, and ease-in-out, or a custom cubic-bezier value like cubic-bezier(0.42, 0, 0.58, 1).

element

string | optional, defaults to "div"

Specify the desired HTML-tag here (eg. <Dip element="li">) in case you don’t want your children wrapped in a div.

optInCssStyles

Array(string) | optional, defaults to an empty array

By default react-dip will morph your components only regarding their sizes and positions using css transforms which is usually a good default regarding performance.
In case you want to morph more css properties you can specify them here, such as optInCssStyles={["borderRadius", "backgroundColor"]}. optional

className, id, style, aria-…, role, etc.

default react / HTML attributes | optional

Any provided standard attribute is passed to the child-container.

Polyfill

As some browsers do not support the Web Animations API, we recommend using the web-animations-js Polyfill.

  1. Install the dependency
  1. $ yarn add web-animations-js
  3. # or using npm
  4. $ npm install --save web-animations-js
  1. include the dependency into your project.
  1. import('web-animations-js') // We recommend dynamic imports to keep initial bundlesize small

Examples

How it works

Basic idea

The basic idea is the following: Every candidate for an animated transition is wrapped in a <Dip ></Dip> Container,
whereas potential start and destination elements get grouped via the same dipId property. Say, if you want to animnate a users name from a list to a detail view
you’d wrap the name in both views in a <Dip dipId={name-${username}}> Container.

Wrapping the Components in a Dip-Container does a couple of things:

  1. registering the Component as a potential transition start point
  2. checking for existing registered elements

If the check for existing registered elements was successfull, we kick in the animation logic, based on the FLIP-technique:

  1. we create a clone of the destination-element including it’s size and position and append this clone on a proper Animation-DOM-Layer
  2. we calculate the css transforms to position the clone at the start position and scale it to the size of the start element
  3. we animate from 2. to 1., hiding the destination-Element whilst animating (currently via web-animations-api, which might change though)

Why a clone?

Whilst a clone has some downsides, such as creating new DOM-Elements just for animating and possible variations in the styling if nested css selectors were used
it gives us more freedom eg. when animating to an element which is inside of a container with overflow: hidden.

Dip-WHAT???

No DEEEE-EYE-PEEE, just dip your taco into some tasty salsa. 🌮

Browser Compatiblity

Chrome Firefox Safari Edge IE iOS
✅ ✅ ✅* ✅* ✅* ✅*

* (requires polyfill)

Caveats (TODO)

  • transitioning to elements in scrolled lists (via browser back)
  • text can get distorted
  • styles from nested queries eg: animating h1 which is styled via section h1 (might be fixable a little bit, not sure if it is worth though, as it is somehow considered bad practices anyhow?)

Inspired by

Huge Thanks to

TODOs

There are tons of ideas for improving react-dip such as adding fine grained control to your transitions, but the primary goal will stay to keep the API as symple as possible.

To be done before anouncing

  • add chapter about polyfilling
  • render props (of course)
  • add support for custom timing functions
  • add complex examples with renderProps, routing etc.
  • add possibility of declaring alternative components that are shown whilst animating
  • add recipie for transitioning lowres- to highres-images
  • export types for flow and typescript
  • add contributing guide lines
  • add error handling for props
  • add error handling for refs
  • move animation to proper element, allowing for parents with overflow: hidden and avoiding z-index issues
  • add Component for Fading in non-dip Elements, after / while a Dip-transions

For some near future milestone

  • add support for staggering
  • add real tests
  • export types for flowtyped and typescript
  • add optional placeholder component that is shown whilst animating
  • add documentation, (maybe even abstractions) for image transitions from low-res to high-res
  • make animation-layer custmizable, so regular items can be in front of them (z-wise)
  • investigate possible optimizations for the scrolling issues