From 79cc7474b5d5b93fda12624517c83347071f867f Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Mon, 21 Oct 2019 00:36:38 +0000 Subject: [PATCH] Deploy website Deploy website version based on 4bcd62ebc45420948b78ba43f0155bdfaf99c96a --- docs/0.18/animated.html | 10 +++++----- docs/0.18/animated/index.html | 10 +++++----- docs/0.18/dimensions.html | 2 +- docs/0.18/dimensions/index.html | 2 +- docs/0.18/imagestore.html | 4 ++-- docs/0.18/imagestore/index.html | 4 ++-- docs/0.18/scrollview.html | 2 +- docs/0.18/scrollview/index.html | 2 +- docs/0.19/dimensions.html | 2 +- docs/0.19/dimensions/index.html | 2 +- docs/0.19/imagestore.html | 4 ++-- docs/0.19/imagestore/index.html | 4 ++-- docs/0.20/dimensions.html | 2 +- docs/0.20/dimensions/index.html | 2 +- docs/0.21/dimensions.html | 2 +- docs/0.21/dimensions/index.html | 2 +- docs/0.22/dimensions.html | 2 +- docs/0.22/dimensions/index.html | 2 +- 18 files changed, 30 insertions(+), 30 deletions(-) diff --git a/docs/0.18/animated.html b/docs/0.18/animated.html index 6e3c946dcd1..65f5a166e08 100644 --- a/docs/0.18/animated.html +++ b/docs/0.18/animated.html @@ -1,4 +1,4 @@ -Animated · React Native
Edit

Animated

Animations are an important part of modern UX, and the Animated library is designed to make them fluid, powerful, and easy to build and maintain.

+
Edit

Animated

Animations are an important part of modern UX, and the Animated library is designed to make them fluid, powerful, and possible to build and maintain.

The simplest workflow is to create an Animated.Value, hook it up to one or more style attributes of an animated component, and then drive updates either via animations, such as Animated.timing, or by hooking into gestures like panning or scrolling via Animated.event. Animated.Value can also bind to props other than style, and can be interpolated as well. Here is a basic example of a container view that will fade in when it's mounted:

class FadeInView extends React.Component {
   constructor(props) {
@@ -96,12 +96,12 @@
   }
 }
-

Note that only animatable components can be animated. View, Text, and Image are already provided, and you can create custom ones with createAnimatedComponent. These special components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.

+

Note that only animatable components can be animated. View, Text, and Image are already provided, and you can create custom ones with createAnimatedComponent. These particular components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.

Animations are heavily configurable. Custom and pre-defined easing functions, delays, durations, decay factors, spring constants, and more can all be tweaked depending on the type of animation.

A single Animated.Value can drive any number of properties, and each property can be run through an interpolation first. An interpolation maps input ranges to output ranges, typically using a linear interpolation but also supports easing functions. By default, it will extrapolate the curve beyond the ranges given, but you can also have it clamp the output value.

For example, you may want to think about your Animated.Value as going from 0 to 1, but animate the position from 150px to 0px and the opacity from 0 to

    -
  1. This can easily be done by modifying style in the example above like so:
    2. +
  2. This can be done by modifying style in the example above like so:
 style={{
    opacity: this.state.fadeAnim, // Binds directly
@@ -113,7 +113,7 @@
    }],
  }}>
-

Animations can also be combined in complex ways using composition functions such as sequence and parallel, and can also be chained together simply by setting the toValue of one animation to be another Animated.Value.

+

Animations can also be combined in complex ways using composition functions such as sequence and parallel, and can also be chained together by setting the toValue of one animation to be another Animated.Value.

Animated.ValueXY is handy for 2D animations, like panning, and there are other helpful additions like setOffset and getLayout to aid with typical interaction patterns, like drag-and-drop.

You can see more example usage in AnimationExample.js, the Gratuitous Animation App, and Animations documentation guide.

Note that Animated is designed to be fully serializable so that animations can be run in a high performance way, independent of the normal JavaScript event loop. This does influence the API, so keep that in mind when it seems a little trickier to do something compared to a fully synchronous system. Checkout Animated.Value.addListener as a way to work around some of these limitations, but use it sparingly since it might have performance implications in the future.

diff --git a/docs/0.18/animated/index.html b/docs/0.18/animated/index.html index 6e3c946dcd1..65f5a166e08 100644 --- a/docs/0.18/animated/index.html +++ b/docs/0.18/animated/index.html @@ -1,4 +1,4 @@ -Animated · React Native
Edit

Animated

Animations are an important part of modern UX, and the Animated library is designed to make them fluid, powerful, and easy to build and maintain.

+
Edit

Animated

Animations are an important part of modern UX, and the Animated library is designed to make them fluid, powerful, and possible to build and maintain.

The simplest workflow is to create an Animated.Value, hook it up to one or more style attributes of an animated component, and then drive updates either via animations, such as Animated.timing, or by hooking into gestures like panning or scrolling via Animated.event. Animated.Value can also bind to props other than style, and can be interpolated as well. Here is a basic example of a container view that will fade in when it's mounted:

class FadeInView extends React.Component {
   constructor(props) {
@@ -96,12 +96,12 @@
   }
 }
-

Note that only animatable components can be animated. View, Text, and Image are already provided, and you can create custom ones with createAnimatedComponent. These special components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.

+

Note that only animatable components can be animated. View, Text, and Image are already provided, and you can create custom ones with createAnimatedComponent. These particular components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.

Animations are heavily configurable. Custom and pre-defined easing functions, delays, durations, decay factors, spring constants, and more can all be tweaked depending on the type of animation.

A single Animated.Value can drive any number of properties, and each property can be run through an interpolation first. An interpolation maps input ranges to output ranges, typically using a linear interpolation but also supports easing functions. By default, it will extrapolate the curve beyond the ranges given, but you can also have it clamp the output value.

For example, you may want to think about your Animated.Value as going from 0 to 1, but animate the position from 150px to 0px and the opacity from 0 to

    -
  1. This can easily be done by modifying style in the example above like so:
    2. +
  2. This can be done by modifying style in the example above like so:
 style={{
    opacity: this.state.fadeAnim, // Binds directly
@@ -113,7 +113,7 @@
    }],
  }}>
-

Animations can also be combined in complex ways using composition functions such as sequence and parallel, and can also be chained together simply by setting the toValue of one animation to be another Animated.Value.

+

Animations can also be combined in complex ways using composition functions such as sequence and parallel, and can also be chained together by setting the toValue of one animation to be another Animated.Value.

Animated.ValueXY is handy for 2D animations, like panning, and there are other helpful additions like setOffset and getLayout to aid with typical interaction patterns, like drag-and-drop.

You can see more example usage in AnimationExample.js, the Gratuitous Animation App, and Animations documentation guide.

Note that Animated is designed to be fully serializable so that animations can be run in a high performance way, independent of the normal JavaScript event loop. This does influence the API, so keep that in mind when it seems a little trickier to do something compared to a fully synchronous system. Checkout Animated.Value.addListener as a way to work around some of these limitations, but use it sparingly since it might have performance implications in the future.

diff --git a/docs/0.18/dimensions.html b/docs/0.18/dimensions.html index e68983dbb58..39c594fa808 100644 --- a/docs/0.18/dimensions.html +++ b/docs/0.18/dimensions.html @@ -80,7 +80,7 @@ 
static set(dims)

This should only be called from native code.

-

@param {object} dims Simple string-keyed object of dimensions to set

+

@param {object} dims string-keyed object of dimensions to set

get()

static get(dim)
diff --git a/docs/0.18/dimensions/index.html b/docs/0.18/dimensions/index.html
index e68983dbb58..39c594fa808 100644
--- a/docs/0.18/dimensions/index.html
+++ b/docs/0.18/dimensions/index.html
@@ -80,7 +80,7 @@
 
static set(dims)
 

 
This should only be called from native code.

-
@param {object} dims Simple string-keyed object of dimensions to set

+
@param {object} dims string-keyed object of dimensions to set

 

 
get()

 
static get(dim)
diff --git a/docs/0.18/imagestore.html b/docs/0.18/imagestore.html
index b9eb16bc4df..1e222a0e634 100644
--- a/docs/0.18/imagestore.html
+++ b/docs/0.18/imagestore.html
@@ -86,7 +86,7 @@
 
removeImageForTag()

 
static removeImageForTag(uri)
 

-
Delete an image from the ImageStore. Images are stored in memory and must be manually removed when you are finished with them, otherwise they will continue to use up RAM until the app is terminated. It is safe to call removeImageForTag() without first calling hasImageForTag(), it will simply fail silently. @platform ios

+
Delete an image from the ImageStore. Images are stored in memory and must be manually removed when you are finished with them, otherwise they will continue to use up RAM until the app is terminated. It is safe to call removeImageForTag() without first calling hasImageForTag(), it will silently fail. @platform ios

 

 
addImageFromBase64()

 
static addImageFromBase64(base64ImageData, success, failure)
@@ -98,7 +98,7 @@
 
static getBase64ForTag(uri, success, failure)
 

 
Retrieves the base64-encoded data for an image in the ImageStore. If the specified URI does not match an image in the store, the failure callback will be called.

-
Note that it is very inefficient to transfer large quantities of binary data between JS and native code, so you should avoid calling this more than necessary. To display an image in the ImageStore, you can just pass the URI to an <Image/> component; there is no need to retrieve the base64 data.

+
Note that it is very inefficient to transfer large quantities of binary data between JS and native code, so you should avoid calling this more than necessary. To display an image in the ImageStore, you can pass the URI to an <Image/> component; there is no need to retrieve the base64 data.
← ImagePickerIOSImage Style Props →
Edit

ScrollView

Component that wraps platform ScrollView while providing integration with touch locking "responder" system.

-

Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.

+

Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector helps to debug.

Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.

Props

    diff --git a/docs/0.18/scrollview/index.html b/docs/0.18/scrollview/index.html index 9bebbd9d2e7..409e6cf46e1 100644 --- a/docs/0.18/scrollview/index.html +++ b/docs/0.18/scrollview/index.html @@ -69,7 +69,7 @@ } });
Edit

ScrollView

Component that wraps platform ScrollView while providing integration with touch locking "responder" system.

-

Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.

+

Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector helps to debug.

Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.

Props

    diff --git a/docs/0.19/dimensions.html b/docs/0.19/dimensions.html index beaeb57cce7..cd501898284 100644 --- a/docs/0.19/dimensions.html +++ b/docs/0.19/dimensions.html @@ -80,7 +80,7 @@ 
    static set(dims)

    This should only be called from native code.

    -

    @param {object} dims Simple string-keyed object of dimensions to set

    +

    @param {object} dims string-keyed object of dimensions to set

    get()

    static get(dim)
diff --git a/docs/0.19/dimensions/index.html b/docs/0.19/dimensions/index.html
index beaeb57cce7..cd501898284 100644
--- a/docs/0.19/dimensions/index.html
+++ b/docs/0.19/dimensions/index.html
@@ -80,7 +80,7 @@
 
    static set(dims)
 
    
 
    This should only be called from native code.
    
-
    @param {object} dims Simple string-keyed object of dimensions to set
    
+
    @param {object} dims string-keyed object of dimensions to set
    
 
    
 
    get()
    
 
    static get(dim)
diff --git a/docs/0.19/imagestore.html b/docs/0.19/imagestore.html
index b4e6da85675..f8dc80df4b9 100644
--- a/docs/0.19/imagestore.html
+++ b/docs/0.19/imagestore.html
@@ -86,7 +86,7 @@
 
    removeImageForTag()
    
 
    static removeImageForTag(uri)
 
    
-
    Delete an image from the ImageStore. Images are stored in memory and must be manually removed when you are finished with them, otherwise they will continue to use up RAM until the app is terminated. It is safe to call removeImageForTag() without first calling hasImageForTag(), it will simply fail silently. @platform ios
    
+
    Delete an image from the ImageStore. Images are stored in memory and must be manually removed when you are finished with them, otherwise they will continue to use up RAM until the app is terminated. It is safe to call removeImageForTag() without first calling hasImageForTag(), it will silently fail. @platform ios
    
 
    
 
    addImageFromBase64()
    
 
    static addImageFromBase64(base64ImageData, success, failure)
@@ -98,7 +98,7 @@
 
    static getBase64ForTag(uri, success, failure)
 
    
 
    Retrieves the base64-encoded data for an image in the ImageStore. If the specified URI does not match an image in the store, the failure callback will be called.
    
-
    Note that it is very inefficient to transfer large quantities of binary data between JS and native code, so you should avoid calling this more than necessary. To display an image in the ImageStore, you can just pass the URI to an <Image/> component; there is no need to retrieve the base64 data.
    
+
    Note that it is very inefficient to transfer large quantities of binary data between JS and native code, so you should avoid calling this more than necessary. To display an image in the ImageStore, you can pass the URI to an <Image/> component; there is no need to retrieve the base64 data.
← ImagePickerIOSImage Style Props →