diff --git a/docs/404.md b/docs/404.md index 259ecac4c..5c0791ac9 100755 --- a/docs/404.md +++ b/docs/404.md @@ -8,4 +8,4 @@ layout: default Crikey! There doesn't seem to be anything here. -If you find a broken link, feel free to send a pull request. You can also let us know at [Github](https://github.com/facebook/AsyncDisplayKit/issues) so that we can fix it. +If you find a broken link, feel free to send a pull request. You can also let us know at [Github](https://github.com/texturegroup/texture/issues) so that we can fix it. diff --git a/docs/README.md b/docs/README.md index 1c83038e7..8c1c2ee54 100755 --- a/docs/README.md +++ b/docs/README.md @@ -1,4 +1,4 @@ -# AsyncDisplayKit Documentation +# Texture Documentation We use [Jekyll](http://jekyllrb.com/) to build the site using Markdown and host it on [Github Pages](https://pages.github.com/). diff --git a/docs/_config.yml b/docs/_config.yml index 6bde53e02..ab347c39b 100755 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -1,6 +1,6 @@ --- -url: http://asyncdisplaykit.org -name: AsyncDisplayKit +url: http://texturegroup.org +name: Texture relative_permalinks: false markdown: kramdown timezone: America/Los_Angeles diff --git a/docs/_docs/accessibility.md b/docs/_docs/accessibility.md index ef13ab944..45261003d 100755 --- a/docs/_docs/accessibility.md +++ b/docs/_docs/accessibility.md @@ -8,4 +8,4 @@ nextPage: layer-backing.html Accessibility works seamlessly in ways that even UIKit doesn’t provide. When using the powerful optimization features of Layer Backing (`.layerBacked`) and Subtree Rasterization (`.shouldRasterizeDescendants`), VoiceOver can access fine-grained metadata about each element. This is pretty amazing: `CALayer` doesn’t support accessibility, and rasterization reduces everything to a single flat image. -The AsyncDisplayKit team fundamentally believes in Accessibility, and invested the time to create an innovative system to make this possible with zero developer effort. As a bonus, this also allows Automated UI Testing greater access to the interface. \ No newline at end of file +The Texture team fundamentally believes in Accessibility, and invested the time to create an innovative system to make this possible with zero developer effort. As a bonus, this also allows Automated UI Testing greater access to the interface. \ No newline at end of file diff --git a/docs/_docs/adoption-guide-2-0-beta1.md b/docs/_docs/adoption-guide-2-0-beta1.md index 26294d534..18591a1ca 100755 --- a/docs/_docs/adoption-guide-2-0-beta1.md +++ b/docs/_docs/adoption-guide-2-0-beta1.md @@ -25,7 +25,7 @@ Add the following to your podfile 
-pod 'AsyncDisplayKit', '>= 2.0'
+pod 'Texture', '>= 2.0'
@@ -36,7 +36,7 @@ then run 
 pod repo update
-pod update AsyncDisplayKit
+pod update Texture
@@ -53,7 +53,7 @@ If your app fails to build instead of just showing the warnings, you might have 1. Disable deprecation warnings in the Xcode project settings 2. Disable warnings as errors in the project's build settings. -3. Disable deprecation warnings in ASDK. To do this, change `line 74` in `ASBaseDefines.h` to `# define ASDISPLAYNODE_WARN_DEPRECATED 0` +3. Disable deprecation warnings in Texture. To do this, change `line 74` in `ASBaseDefines.h` to `# define ASDISPLAYNODE_WARN_DEPRECATED 0` Once your app builds and runs, test it to make sure everything is working normally. If you find any problems, try adopting the new API in that area and re-test. @@ -71,7 +71,7 @@ A full API changelog from `1.9.92` to `2.0-beta.1` is available Automatic Subnode Management API has been moved out of Beta, but has a few documented [limitations](). +- ASDisplayNode's `.usesImplicitHierarchyManagement` has been renamed to `.automaticallyManagesSubnodes`. The Automatic Subnode Management API has been moved out of Beta, but has a few documented [limitations](). - ASDisplayNode's `-cancelLayoutTransitionsInProgress` has been renamed to `-cancelLayoutTransition`. The Layout Transition API has been moved out of Beta. Significant new functionality is planed for future dot releases. @@ -92,11 +92,11 @@ These new methods replace the following: #### Collection / Table API Updates -AsyncDisplayKit's collection and table APIs have been moved from the view space (`collectionView`, `tableView`) to the node space (`collectionNode`, `tableNode`). +Texture's collection and table APIs have been moved from the view space (`collectionView`, `tableView`) to the node space (`collectionNode`, `tableNode`). - Search your project for `tableView` and `collectionView`. Most, if not all, of the data source / delegate methods have new node versions. -It is important that developers using AsyncDisplayKit understand that an ASCollectionNode is backed by an ASCollectionView (a subclass of UICollectionView). ASCollectionNode runs asynchronously, so calling number -numberOfRowsInSection on the collectionNode is different than calling it on the collectionView. +It is important that developers using Texture understand that an ASCollectionNode is backed by an ASCollectionView (a subclass of UICollectionView). ASCollectionNode runs asynchronously, so calling number -numberOfRowsInSection on the collectionNode is different than calling it on the collectionView. For example, let's say you have an empty table. You insert `100` rows and then immediately call -tableView:numberOfRowsInSection. This will return `0` rows. If you call -waitUntilAllUpdatesAreCommitted after insertion (waits until the collectionNode synchronizes with the collectionView), you will get 100, _but_ you might block the main thread. A good developer should rarely (or never) need to use -waitUntilAllUpdatesAreCommitted. If you update the collectionNode and then need to read back immediately, you should use the collectionNode API. You shouldn't need to talk to the collectionView. @@ -134,7 +134,7 @@ Resources: - [Video](https://youtu.be/yuDqvE5n_1g) of the ASCollectionNode Behind-the-Scenes talk at Pinterest. The diagrams seen in the talk. -- PR [#2390](https://github.com/facebook/AsyncDisplayKit/pull/2390) and PR [#2381](https://github.com/facebook/AsyncDisplayKit/pull/2381) show how we converted AsyncDisplayKit's [example projects](https://github.com/facebook/AsyncDisplayKit/tree/master/examples) to conform to this new API. +- PR [#2390](https://github.com/facebook/AsyncDisplayKit/pull/2390) and PR [#2381](https://github.com/facebook/AsyncDisplayKit/pull/2381) show how we converted AsyncDisplayKit's [example projects](https://github.com/texturegroup/texture/tree/master/examples) to conform to this new API. #### Layout API Updates diff --git a/docs/_docs/asenvironment.md b/docs/_docs/asenvironment.md index b2e0432c2..c749cd080 100755 --- a/docs/_docs/asenvironment.md +++ b/docs/_docs/asenvironment.md @@ -12,8 +12,8 @@ Any object that conforms to the `` protocol can propagate specifi Compared to UIKit, this system is very efficient and one of the reasons why nodes are much lighter weight than UIViews. This is achieved by using simple structures to store data rather than creating objects. For example, `UITraitCollection` is an object, but `ASEnvironmentTraitCollection` is just a struct. -This means that whenever a node needs to query something about its environment, for example to check its [interface state](http://asyncdisplaykit.org/docs/intelligent-preloading.html#interface-state-ranges), instead of climbing the entire tree or checking all of its children, it can go to one spot and read the value that was propogated to it. +This means that whenever a node needs to query something about its environment, for example to check its [interface state](http://texturegroup.org/docs/intelligent-preloading.html#interface-state-ranges), instead of climbing the entire tree or checking all of its children, it can go to one spot and read the value that was propogated to it. A key operating principle of ASEnvironment is to update values when new subnodes are added or removed. -ASEnvironment powers many of the most valuable features of AsyncDisplayKit. **There is no public API available at this time.** +ASEnvironment powers many of the most valuable features of Texture. **There is no public API available at this time.** diff --git a/docs/_docs/asrunloopqueue.md b/docs/_docs/asrunloopqueue.md index 243440877..cd2e978c2 100755 --- a/docs/_docs/asrunloopqueue.md +++ b/docs/_docs/asrunloopqueue.md @@ -5,10 +5,10 @@ permalink: /docs/asrunloopqueue.html prevPage: asenvironment.html --- -Even with main thread work, AsyncDisplayKit is able to dramatically reduce its impact on the user experience by way of the rather amazing ASRunLoopQueue. +Even with main thread work, Texture is able to dramatically reduce its impact on the user experience by way of the rather amazing ASRunLoopQueue. `ASRunloopQueue` breaks up operations that must be performed on the main thread into far smaller chunks, easily 1/10th of the size that they otherwise would be, so that operation such as allocating UIViews or even destroying objects can be spread out and allow the run loops to more frequently turn. This more periodic turning allows the device to much more frequently check if a user touch has started or if an animation timer requires a new frame to be drawn, allowing far greater responsiveness even when the device is very busy and processing a large queue of main thread work. -It's a longer discussion why this kind of technique is extremely challenging to implement with `UIKit`, but it has to do with the fact that `AsyncDisplayKit` prepares content in advance, giving it a buffer of time where it can spread out the creation of these objects in tiny chunks. If it doesn't finish by the time it needs to be on screen, then it finishes the rest of what needs to be created in a single chunk. `UIKit` has no similar mechanisms to create things in advance, and there is always just one huge chunk as a view controller or cell needs to come on screen. +It's a longer discussion why this kind of technique is extremely challenging to implement with `UIKit`, but it has to do with the fact that `Texture` prepares content in advance, giving it a buffer of time where it can spread out the creation of these objects in tiny chunks. If it doesn't finish by the time it needs to be on screen, then it finishes the rest of what needs to be created in a single chunk. `UIKit` has no similar mechanisms to create things in advance, and there is always just one huge chunk as a view controller or cell needs to come on screen. -**ASRunLoopQueue is enabled by default when running AsyncDisplayKit.** A developer does not need to be aware of it's existence except to know that it helps reduce main thread blockage. +**ASRunLoopQueue is enabled by default when running Texture.** A developer does not need to be aware of it's existence except to know that it helps reduce main thread blockage. diff --git a/docs/_docs/automatic-layout-basics.md b/docs/_docs/automatic-layout-basics.md index 85b50d3ef..8a830b1cd 100755 --- a/docs/_docs/automatic-layout-basics.md +++ b/docs/_docs/automatic-layout-basics.md @@ -12,11 +12,11 @@ ASLayout is an automatic, asynchronous, purely Objective-C box model layout feat `UIView` instances store position and size in their `center` and `bounds` properties. As constraints change, Core Animation performs a layout pass to call `layoutSubviews`, asking views to update these properties on their subviews. -`` instances (all ASDisplayNodes and subclasses) do not have any size or position information. Instead, AsyncDisplayKit calls the `layoutSpecThatFits:` method with a given size constraint and the component must return a structure describing both its size, and the position and sizes of its children. +`` instances (all ASDisplayNodes and subclasses) do not have any size or position information. Instead, Texture calls the `layoutSpecThatFits:` method with a given size constraint and the component must return a structure describing both its size, and the position and sizes of its children. ##Terminology -The terminology is a bit confusing, so here is a brief description of all of the ASDK automatic layout players: +The terminology is a bit confusing, so here is a brief description of all of the Texture automatic layout players: Items that conform to the **\ protocol** declares a method for measuring the layout of an object. A layout is defined by an ASLayout return value, and must specify 1) the size (but not position) of the layoutable object, and 2) the size and position of all of its immediate child objects. The tree recursion is driven by parents requesting layouts from their children in order to determine their size, followed by the parents setting the position of the children once the size is known. @@ -24,7 +24,7 @@ This protocol also implements a "family" of layoutable protocols - the `AS{*}Lay All ASDisplayNodes and subclasses as well as the `ASLayoutSpecs` conform to this protocol. -An **`ASLayoutSpec`** is an immutable object that describes a layout. Creation of a layout spec should only happen by a user in layoutSpecThatFits:. During that method, a layout spec can be created and mutated. Once it is passed back to ASDK, the isMutable flag will be set to NO and any further mutations will cause an assert. +An **`ASLayoutSpec`** is an immutable object that describes a layout. Creation of a layout spec should only happen by a user in layoutSpecThatFits:. During that method, a layout spec can be created and mutated. Once it is passed back to Texture, the isMutable flag will be set to NO and any further mutations will cause an assert. Every ASLayoutSpec must act on at least one child. The ASLayoutSpec has the responsibility of holding on to the spec children. Some layout specs, like ASInsetLayoutSpec, only require a single child. Others, have multiple. diff --git a/docs/_docs/automatic-layout-containers.md b/docs/_docs/automatic-layout-containers.md index 05655ee56..436d9c6ef 100755 --- a/docs/_docs/automatic-layout-containers.md +++ b/docs/_docs/automatic-layout-containers.md @@ -6,7 +6,7 @@ prevPage: scroll-node.html nextPage: layout-api-debugging.html --- -AsyncDisplayKit includes a library of `layoutSpec` components that can be composed to declaratively specify a layout. +Texture includes a library of `layoutSpec` components that can be composed to declaratively specify a layout. The **child(ren) of a layoutSpec may be a node, a layoutSpec or a combination of the two types.** In the below image, an `ASStackLayoutSpec` (vertical) containing a text node and an image node, is wrapped in another `ASStackLayoutSpec` (horizontal) with another text node. @@ -47,7 +47,7 @@ Both nodes and layoutSpecs conform to the `` protocol. Any `ASLay ASLayoutSpec -

Can be used as a spacer in a stack spec with other children, when .flexGrow and/or .flexShrink is applied.

This class can also be subclassed to create custom layout specs - advanced ASDK only!

+

Can be used as a spacer in a stack spec with other children, when .flexGrow and/or .flexShrink is applied.

This class can also be subclassed to create custom layout specs - advanced Texture only!

@@ -138,7 +138,7 @@ The following properties may be set on any node or `layoutSpec`s, but will only ### Providing Intrinsic Sizes for Leaf Nodes -AsyncDisplayKit's layout is recursive, starting at the layoutSpec returned from `layoutSpecThatFits:` and proceeding down until it reaches the leaf nodes included in any nested `layoutSpec`s. +Texture's layout is recursive, starting at the layoutSpec returned from `layoutSpecThatFits:` and proceeding down until it reaches the leaf nodes included in any nested `layoutSpec`s. Some leaf nodes provide their own intrinsic size, such as `ASTextNode` or `ASImageNode`. An attributed string or an image have their own sizes. Other leaf nodes require an intrinsic size to be set. @@ -187,6 +187,6 @@ An inset spec requires its object to have an intrinsic size. It adds the inset p ### Best Practices - - AsyncDisplayKit layout is called on a background thread. Do not access the device screen bounds, or any other UIKit methods in `layoutSpecThatFits:`. + - Texture layout is called on a background thread. Do not access the device screen bounds, or any other UIKit methods in `layoutSpecThatFits:`. - don't wrap everything in a staticLayoutSpec? - avoid using preferred frame size for everything - won't respond nicely to device rotation or device sizing differences? diff --git a/docs/_docs/automatic-layout-examples-2.md b/docs/_docs/automatic-layout-examples-2.md index eb55c2f5f..07da8df13 100755 --- a/docs/_docs/automatic-layout-examples-2.md +++ b/docs/_docs/automatic-layout-examples-2.md @@ -6,7 +6,7 @@ prevPage: layout2-quickstart.html nextPage: layout2-layoutspec-types.html --- -Check out the layout specs example project to play around with the code below. +Check out the layout specs example project to play around with the code below. ## Simple Header with Left and Right Justified Text @@ -161,7 +161,7 @@ override func layoutSpecThatFits(_ constrainedSize: ASSizeRange) -> ASLayoutSpec let absoluteSpec = ASAbsoluteLayoutSpec(children: [photoNode, iconNode]) - // ASAbsoluteLayoutSpec's .sizing property recreates the behavior of ASDK Layout API 1.0's "ASStaticLayoutSpec" + // ASAbsoluteLayoutSpec's .sizing property recreates the behavior of Texture Layout API 1.0's "ASStaticLayoutSpec" absoluteSpec.sizing = .sizeToFit return absoluteSpec; diff --git a/docs/_docs/automatic-layout-examples.md b/docs/_docs/automatic-layout-examples.md index 7b2b41399..152372093 100755 --- a/docs/_docs/automatic-layout-examples.md +++ b/docs/_docs/automatic-layout-examples.md @@ -92,7 +92,7 @@ Three examples in increasing order of complexity. ###Discussion -Get the full ASDK project at examples/ASDKgram. +Get the full Texture project at examples/ASDKgram. #Social App Layout 2 @@ -201,4 +201,4 @@ Get the full ASDK project at examples/ASDKgram. ###Discussion -Get the full ASDK project at examples/CatDealsCollectionView. +Get the full Texture project at examples/CatDealsCollectionView. diff --git a/docs/_docs/automatic-subnode-mgmt.md b/docs/_docs/automatic-subnode-mgmt.md index 8ef16a6b6..e4ff53420 100755 --- a/docs/_docs/automatic-subnode-mgmt.md +++ b/docs/_docs/automatic-subnode-mgmt.md @@ -12,7 +12,7 @@ When enabled, ASM means that your nodes no longer require `addSubnode:` or `remo ### Example ###
-Consider the following intialization method from the PhotoCellNode class in ASDKgram sample app. This ASCellNode subclass produces a simple social media photo feed cell. +Consider the following intialization method from the PhotoCellNode class in ASDKgram sample app. This ASCellNode subclass produces a simple social media photo feed cell. In the "Original Code" we see the familiar `addSubnode:` calls in bold. In the "Code with ASM" these have been removed and replaced with a single line that enables ASM. @@ -287,7 +287,7 @@ The `_userAvatarImageNode`, `_photoImageNode`, and `_photoCommentsNode` are adde An appropriately constructed ASLayoutSpec will know which subnodes need to be added, removed or animated. -Try out the ASDKgram sample app after looking at the code above, and you will see how simple it is to code an `ASCellNode` whose layout is responsive to numerous, individual data fetches and returns. While the `ASLayoutSpec` is coded in a way that leaves holes for the avatar and photo to populate, you can see how the cell's height will automatically adjust to accomodate the comments node at the bottom of the photo. +Try out the ASDKgram sample app after looking at the code above, and you will see how simple it is to code an `ASCellNode` whose layout is responsive to numerous, individual data fetches and returns. While the `ASLayoutSpec` is coded in a way that leaves holes for the avatar and photo to populate, you can see how the cell's height will automatically adjust to accomodate the comments node at the bottom of the photo. This is just a simple example, but this feature has many more powerful uses. diff --git a/docs/_docs/batch-fetching-api.md b/docs/_docs/batch-fetching-api.md index 4cb153e24..5fd904469 100755 --- a/docs/_docs/batch-fetching-api.md +++ b/docs/_docs/batch-fetching-api.md @@ -6,7 +6,7 @@ prevPage: hit-test-slop.html nextPage: automatic-subnode-mgmt.html --- -AsyncDisplayKit's Batch Fetching API makes it easy to add fetching chunks of new data. Usually this would be done in a `-scrollViewDidScroll:` method, but ASDK provides a more structured mechanism. +Texture's Batch Fetching API makes it easy to add fetching chunks of new data. Usually this would be done in a `-scrollViewDidScroll:` method, but Texture provides a more structured mechanism. By default, as a user is scrolling, when they approach the point in the table or collection where they are 2 "screens" away from the end of the current content, the table will try to fetch more data. @@ -140,12 +140,12 @@ func tableNode(tableNode: ASTableNode, willBeginBatchFetchWithContext context: A -Once you've finished fetching your data, it is very important to let ASDK know that you have finished the process. To do that, you need to call `-completeBatchFetching:` on the `context` object that was passed in with a parameter value of `YES`. This assures that the whole batch fetching mechanism stays in sync and the next batch fetching cycle can happen. Only by passing `YES` will the context know to attempt another batch update when necessary. +Once you've finished fetching your data, it is very important to let Texture know that you have finished the process. To do that, you need to call `-completeBatchFetching:` on the `context` object that was passed in with a parameter value of `YES`. This assures that the whole batch fetching mechanism stays in sync and the next batch fetching cycle can happen. Only by passing `YES` will the context know to attempt another batch update when necessary. Check out the following sample apps to see the batch fetching API in action: diff --git a/docs/_docs/cell-node.md b/docs/_docs/cell-node.md index 5bf99b5ee..10fa271cf 100755 --- a/docs/_docs/cell-node.md +++ b/docs/_docs/cell-node.md @@ -6,11 +6,11 @@ prevPage: display-node.html nextPage: button-node.html --- -`ASCellNode`, as you may have guessed, is the cell class of ASDK. Unlike the various cells in UIKit, `ASCellNode` can be used with `ASTableNodes`, `ASCollectionNodes` and `ASPagerNodes`, making it incredibly flexible. +`ASCellNode`, as you may have guessed, is the cell class of Texture. Unlike the various cells in UIKit, `ASCellNode` can be used with `ASTableNodes`, `ASCollectionNodes` and `ASPagerNodes`, making it incredibly flexible. ### 3 Ways to Party -There are three ways in which you can implement the cells you'll use in your ASDK app: subclassing `ASCellNode`, initializing with an existing `ASViewController` or using an existing UIView or `CALayer`. +There are three ways in which you can implement the cells you'll use in your Texture app: subclassing `ASCellNode`, initializing with an existing `ASViewController` or using an existing UIView or `CALayer`. #### Subclassing @@ -127,10 +127,10 @@ node.neverShowPlaceholders = true -With this property set to `YES`, the main thread will be blocked until display has completed for the cell. This is more similar to UIKit, and in fact makes AsyncDisplayKit scrolling visually indistinguishable from UIKit's, except being faster. +With this property set to `YES`, the main thread will be blocked until display has completed for the cell. This is more similar to UIKit, and in fact makes Texture scrolling visually indistinguishable from UIKit's, except being faster.
-Using this option does not eliminate all of the performance advantages of AsyncDisplayKit. Normally, a cell has been preloading and is almost done when it reaches the screen, so the blocking time is very short. Even if the rangeTuningParameters are set to 0 this option outperforms UIKit. While the main thread is waiting, subnode display executes concurrently. +Using this option does not eliminate all of the performance advantages of Texture. Normally, a cell has been preloading and is almost done when it reaches the screen, so the blocking time is very short. Even if the rangeTuningParameters are set to 0 this option outperforms UIKit. While the main thread is waiting, subnode display executes concurrently.
### `UITableViewCell` specific propertys diff --git a/docs/_docs/containers-ascollectionnode.md b/docs/_docs/containers-ascollectionnode.md index 676bac3bb..d19074a3a 100755 --- a/docs/_docs/containers-ascollectionnode.md +++ b/docs/_docs/containers-ascollectionnode.md @@ -118,7 +118,7 @@ In the example above, you can see how the index is used to access the photo mode ### Replacing a UICollectionViewController with an ASViewController -AsyncDisplayKit does not offer an equivalent to UICollectionViewController. Instead, you can use the flexibility of ASViewController to recreate any type of UI...ViewController. +Texture does not offer an equivalent to UICollectionViewController. Instead, you can use the flexibility of ASViewController to recreate any type of UI...ViewController. Consider, the following ASViewController subclass. @@ -160,7 +160,7 @@ init() { This works just as well with any node including as an ASTableNode, ASPagerNode, etc. ### Accessing the ASCollectionView -If you've used previous versions of ASDK, you'll notice that `ASCollectionView` has been removed in favor of `ASCollectionNode`. +If you've used previous versions of Texture, you'll notice that `ASCollectionView` has been removed in favor of `ASCollectionNode`.
`ASCollectionView`, an actual `UICollectionView` subclass, is still used internally by `ASCollectionNode`. While it should not be created directly, it can still be used directly by accessing the `.view` property of an `ASCollectionNode`. @@ -208,15 +208,15 @@ Soon, there will be a method such as `ASTableNode`'s `-constrainedSizeForRow:` b ### Examples -The most detailed example of laying out the cells of an `ASCollectionNode` is the CustomCollectionView app. It includes a Pinterest style cell layout using an `ASCollectionNode` and a custom `UICollectionViewLayout`. +The most detailed example of laying out the cells of an `ASCollectionNode` is the CustomCollectionView app. It includes a Pinterest style cell layout using an `ASCollectionNode` and a custom `UICollectionViewLayout`. #### More Sample Apps with ASCollectionNodes ### Interoperability with UICollectionViewCells diff --git a/docs/_docs/containers-asnodecontroller.md b/docs/_docs/containers-asnodecontroller.md index 987f21092..7dd5034da 100755 --- a/docs/_docs/containers-asnodecontroller.md +++ b/docs/_docs/containers-asnodecontroller.md @@ -10,13 +10,13 @@ nextPage: containers-astablenode.html To use this feature, you will need to import "ASNodeController+Beta.h"
-The ASDK team has many exciting ideas for expanding `ASNodeController`. Follow along [here](https://github.com/facebook/AsyncDisplayKit/issues/2964) if you'd like to participate in shaping the future of node controllers. +The Texture team has many exciting ideas for expanding `ASNodeController`. Follow along [here](https://github.com/facebook/AsyncDisplayKit/issues/2964) if you'd like to participate in shaping the future of node controllers. For now, `ASNodeController` remains a simple, but powerful class. ### Example -The [example project](https://github.com/facebook/AsyncDisplayKit/pull/2945) attached in the initial PR modifies the normal [ASDKgram](https://github.com/facebook/AsyncDisplayKit/tree/master/examples/ASDKgram) project to use an `ASNodeController`. +The [example project](https://github.com/texturegroup/texture/pull/2945) attached in the initial PR modifies the normal [ASDKgram](https://github.com/texturegroup/texture/tree/master/examples/ASDKgram) project to use an `ASNodeController`. This `PhotoCellNodeController` is used to manage the fetching of the comments data for a photo in a photo feed, once the photo enters the preload range. This node controller allows us to separate the preloading logic from where it previously existed in the `PhotoCellNode` "view" class. To convert ASDKgram to use an `ASNodeController`, we first create a `PhotoCellNodeController` class. @@ -106,7 +106,7 @@ Next, we add a mutable array to the `PhotoFeedNodeController` to store our node self = [super initWithNode:_tableNode]; if (self) { - self.navigationItem.title = @"ASDK"; + self.navigationItem.title = @"Texture"; [self.navigationController setNavigationBarHidden:YES]; _tableNode.dataSource = self; @@ -129,7 +129,7 @@ final class PhotoFeedNodeController: PhotoFeedBaseController { init() { super.init(node: tableNode) - navigationItem.title = "ASDK" + navigationItem.title = "Texture" navigationController.isNavigationBarHidden = true tableNode.dataSource = self diff --git a/docs/_docs/containers-aspagernode.md b/docs/_docs/containers-aspagernode.md index 918e297fb..31b6e091a 100755 --- a/docs/_docs/containers-aspagernode.md +++ b/docs/_docs/containers-aspagernode.md @@ -155,12 +155,12 @@ To resolve the error message add `[self.pagerNode waitUntilAllUpdatesAreCommitte Unfortunately the disadvantage of this is that the first measurement pass will block the main thread until it finishes. #### Some more details about the error messages above -The reason for this error message is that due to the asynchronous nature of AsyncDisplayKit, measurement of nodes will happen on a background thread as UIKit will resize the view of the `ASViewController` on on the main thread. The new layout pass has to wait until the old layout pass finishes with an old layout constrained size. Unfortunately while the measurement pass with the old constrained size is still in progress the `ASPagerFlowLayout` that is backing a `ASPagerNode` will print some errors in the console as it expects sizes for nodes already measured with the new constrained size. +The reason for this error message is that due to the asynchronous nature of Texture, measurement of nodes will happen on a background thread as UIKit will resize the view of the `ASViewController` on on the main thread. The new layout pass has to wait until the old layout pass finishes with an old layout constrained size. Unfortunately while the measurement pass with the old constrained size is still in progress the `ASPagerFlowLayout` that is backing a `ASPagerNode` will print some errors in the console as it expects sizes for nodes already measured with the new constrained size. ### Sample Apps Check out the following sample apps to see an `ASPagerNode` in action: diff --git a/docs/_docs/containers-astablenode.md b/docs/_docs/containers-astablenode.md index 8227da117..7742e23c3 100755 --- a/docs/_docs/containers-astablenode.md +++ b/docs/_docs/containers-astablenode.md @@ -76,9 +76,9 @@ Note that neither of these methods require a reuse mechanism. ### Replacing UITableViewController with ASViewController -AsyncDisplayKit does not offer an equivalent to `UITableViewController`. Instead, use an `ASViewController` initialized with an `ASTableNode`. +Texture does not offer an equivalent to `UITableViewController`. Instead, use an `ASViewController` initialized with an `ASTableNode`. -Consider, again, the `ASViewController` subclass - PhotoFeedNodeController - from the `ASDKgram sample app` that uses a table node as its managed node. +Consider, again, the `ASViewController` subclass - PhotoFeedNodeController - from the `ASDKgram sample app` that uses a table node as its managed node. An `ASTableNode` is assigned to be managed by an `ASViewController` in its `-initWithNode:` designated initializer method. @@ -120,7 +120,7 @@ init(models: [Model]) { It is very important that node blocks be thread-safe. One aspect of that is ensuring that the data model is accessed _outside_ of the node block. Therefore, it is unlikely that you should need to use the index inside of the block. -Consider the following `-tableNode:nodeBlockForRowAtIndexPath:` method from the `PhotoFeedNodeController.m` file in the ASDKgram sample app. +Consider the following `-tableNode:nodeBlockForRowAtIndexPath:` method from the `PhotoFeedNodeController.m` file in the ASDKgram sample app.
SwiftObjective-C @@ -164,7 +164,7 @@ In the example above, you can see how the index is used to access the photo mode ### Accessing the ASTableView -If you've used previous versions of ASDK, you'll notice that `ASTableView` has been removed in favor of `ASTableNode`. +If you've used previous versions of Texture, you'll notice that `ASTableView` has been removed in favor of `ASTableNode`.
ASTableView, an actual UITableView subclass, is still used internally by ASTableNode. While it should not be created directly, it can still be used directly by accessing the .view property of an ASTableNode. @@ -216,13 +216,13 @@ This is all to say, a `tableNode`'s cells will always fill the full width of the If you call `-setNeedsLayout` on an `ASCellNode`, it will automatically perform another layout pass and if its overall desired size has changed, the table will be informed and will update itself. -This is different from `UIKit` where normally you would have to call reload row / item. This saves tons of code, check out the ASDKgram sample app to see side by side implementations of an `UITableView` and `ASTableNode` implemented social media feed. +This is different from `UIKit` where normally you would have to call reload row / item. This saves tons of code, check out the ASDKgram sample app to see side by side implementations of an `UITableView` and `ASTableNode` implemented social media feed. ### Sample Apps using ASTableNode diff --git a/docs/_docs/containers-asviewcontroller.md b/docs/_docs/containers-asviewcontroller.md index 6c4962ae5..53f91a784 100755 --- a/docs/_docs/containers-asviewcontroller.md +++ b/docs/_docs/containers-asviewcontroller.md @@ -22,7 +22,7 @@ More features will be added over time, so it is a good idea to base your view co A `UIViewController` provides a view of its own. An `ASViewController` is assigned a node to manage in its designated initializer `-initWithNode:`. -Consider the following `ASViewController` subclass, `PhotoFeedNodeController`, from the ASDKgram example project that would like to use a table node as its managed node. +Consider the following `ASViewController` subclass, `PhotoFeedNodeController`, from the ASDKgram example project that would like to use a table node as its managed node. This table node is assigned to the `ASViewController` in its `-initWithNode:` designated initializer method. diff --git a/docs/_docs/containers-overview.md b/docs/_docs/containers-overview.md index 7d55b0c4c..335020541 100755 --- a/docs/_docs/containers-overview.md +++ b/docs/_docs/containers-overview.md @@ -7,11 +7,11 @@ nextPage: node-overview.html --- ### Use Nodes in Node Containers -It is highly recommended that you use AsyncDisplayKit's nodes within a node container. AsyncDisplayKit offers the following node containers. +It is highly recommended that you use Texture's nodes within a node container. Texture offers the following node containers. - + @@ -43,10 +43,10 @@ It is highly recommended that you use AsyncDisplayKit's nodes within a node cont
Example code and specific sample projects are highlighted in the documentation for each node container. - + ### What do I Gain by Using a Node Container? A node container automatically manages the intelligent preloading of its nodes. This means that all of the node's layout measurement, data fetching, decoding and rendering will be done asynchronously. Among other conveniences, this is why it is recommended to use nodes within a container node. -Note that while it _is_ possible to use nodes directly (without an AsyncDisplayKit node container), unless you add additional calls, they will only start displaying once they come onscreen (as UIKit does). This can lead to performance degredation and flashing of content. +Note that while it _is_ possible to use nodes directly (without an Texture node container), unless you add additional calls, they will only start displaying once they come onscreen (as UIKit does). This can lead to performance degredation and flashing of content. diff --git a/docs/_docs/control-node.md b/docs/_docs/control-node.md index 4032af0c6..30aef3291 100755 --- a/docs/_docs/control-node.md +++ b/docs/_docs/control-node.md @@ -6,7 +6,7 @@ prevPage: map-node.html nextPage: scroll-node.html --- -`ASControlNode` is the ASDK equivalent to `UIControl`. You don't create instances of `ASControlNode` directly. Instead, you can use it as a subclassing point when creating controls of your own. In fact, ASTextNode, ASImageNode, ASVideoNode and ASMapNode are all subclasses of `ASControlNode`. +`ASControlNode` is the Texture equivalent to `UIControl`. You don't create instances of `ASControlNode` directly. Instead, you can use it as a subclassing point when creating controls of your own. In fact, ASTextNode, ASImageNode, ASVideoNode and ASMapNode are all subclasses of `ASControlNode`. This fact is especially useful when it comes to image and text nodes. Having the ability to add target-action pairs means that you can use any text or image node as a button without having to rely on creating gesture recognizers, as you would with text in UIKit, or creating extraneous views as you might when using `UIButton`. diff --git a/docs/_docs/corner-rounding.md b/docs/_docs/corner-rounding.md index 240b17410..27601c8c3 100755 --- a/docs/_docs/corner-rounding.md +++ b/docs/_docs/corner-rounding.md @@ -12,7 +12,7 @@ When it comes to corner rounding, many developers stick with CALayer's `.cornerR
  • why you shouldn’t use CALayer’s .cornerRadius
  • more performant corner rounding options and when to use them
  • a flow chart for choosing your ideal corner rounding strategy
    • -
  • AsyncDisplayKit corner rounding methods
    • +
  • Texture corner rounding methods
    • ## CALayer's .cornerRadius is Expensive @@ -61,10 +61,10 @@ The second method involves using bezier paths with **precomposited alpha corners A key limitation of precomposited corners is that the corners must only touch one node and not intersect with any subnodes. If either of these conditions exist, clip corners must be used. -Note that AsyncDisplayKit nodes have a special optimization of `.cornerRadius` that automatically implements precomposited corners **only when using** `.shouldRasterizeDescendants`. It's important to think carefully before you enable rasterization, so don't use this option without first reading all about the concept. +Note that Texture nodes have a special optimization of `.cornerRadius` that automatically implements precomposited corners **only when using** `.shouldRasterizeDescendants`. It's important to think carefully before you enable rasterization, so don't use this option without first reading all about the concept.
    -If you're looking for a simple, flat-color rounded rectangle or circle, AsyncDisplayKit offers a variety of conveniences to provide this. See `UIImage+ASConveniences.h` for methods to create flat-colored, rounded-corner resizable images using precomposited corners (both alpha and opaque are supported). These are great for use as placeholders for image nodes or backgrounds for ASButtonNode. More precomposited corner methods will be released with AsyncDisplayKit 2.0 release. +If you're looking for a simple, flat-color rounded rectangle or circle, Texture offers a variety of conveniences to provide this. See `UIImage+ASConveniences.h` for methods to create flat-colored, rounded-corner resizable images using precomposited corners (both alpha and opaque are supported). These are great for use as placeholders for image nodes or backgrounds for ASButtonNode. More precomposited corner methods will be released with Texture 2.0 release.
    ### Clip Corner @@ -81,7 +81,7 @@ Clip corners applies to two main types of corner rounding situations:
    -Check back soon! Clip corner methods may be released in AsyncDisplayKit 2.0 release. +Check back soon! Clip corner methods may be released in Texture 2.0 release.
    ## Is it ever okay to use CALayer's .cornerRadius property? @@ -94,7 +94,7 @@ It is much less bad, and okay as a shortcut, to use `.cornerRadius.` for screens Some people have suggested that using CALayer's `.shouldRasterize` can improve the performance of the `.cornerRadius` property. This is not well understood option that is generally perilous. As long as nothing causes it to re-rasterize (no movement, no tap to change color, not on a table view that moves, etc), it is okay to use. Generally we don't encourage this because it is very easy to cause much worse performance. For people who have not great app architecture and insist on using CALayer's `.cornerRadius` (e.g. their app is not very performant), this _can_ make a meaningful difference. However, if you are building your app from the ground up, we highly reccommend that you choose one of the better corner rounding strategies above. -CALayer's `.shouldRasterize` is unrelated to AsyncDisplayKit `node.shouldRasterizeDescendents`. When enabled, `.shouldRasterizeDescendents` will prevent the actual view and layer of the subnode children from being created. +CALayer's `.shouldRasterize` is unrelated to Texture `node.shouldRasterizeDescendents`. When enabled, `.shouldRasterizeDescendents` will prevent the actual view and layer of the subnode children from being created. ## Corner Rounding Strategy Flowchart diff --git a/docs/_docs/debug-tool-ASRangeController.md b/docs/_docs/debug-tool-ASRangeController.md index fcc2d124d..b1bbc33a8 100755 --- a/docs/_docs/debug-tool-ASRangeController.md +++ b/docs/_docs/debug-tool-ASRangeController.md @@ -16,9 +16,9 @@ This debug feature adds a semi-transparent subview in the bottom right hand corn - The white debug label above the RangeController bar displays the RangeController dataSource’s class name to differentiate between nested views. - The overlay can be moved with a panning gesture in order to see content under it. -This debug feature is useful for highly optimized ASDK apps that require tuning of any ASRangeController. Or for anyone who is curious about how ASRangeControllers work. +This debug feature is useful for highly optimized Texture apps that require tuning of any ASRangeController. Or for anyone who is curious about how ASRangeControllers work. -The VerticalWithinHorizontal example app contains an ASPagerNode with embedded ASTableViews. In the screenshot with this feature enabled, you can see the two range controllers - ASTableView and ASCollectionView (ASPagerNode) - in the overlay. +The VerticalWithinHorizontal example app contains an ASPagerNode with embedded ASTableViews. In the screenshot with this feature enabled, you can see the two range controllers - ASTableView and ASCollectionView (ASPagerNode) - in the overlay. - The white arrows to the right of the rangeController bars indicate that the user is currently scrolling down through the table and right through the ASCollectionView/PagerNode. - The ASTableView rangeController bar indicates that the range parameters are tuned to both fetch and decode more data in the downward table direction rather than in the reverse direction (which makes sense as the user is scrolling down). diff --git a/docs/_docs/faq.md b/docs/_docs/faq.md index d188c76e1..fa7a7826f 100755 --- a/docs/_docs/faq.md +++ b/docs/_docs/faq.md @@ -26,8 +26,8 @@ nextPage: containers-asviewcontroller.html ### Common Questions @@ -59,7 +59,7 @@ Although the block is destroyed after the view is created, in the event that the ### ASCellNode Reusability
    -AsyncDisplayKit does not use cell reuse, for a number of specific reasons, one side effect of this is that it eliminates the large class of bugs associated with cell reuse. +Texture does not use cell reuse, for a number of specific reasons, one side effect of this is that it eliminates the large class of bugs associated with cell reuse.
    ### LayoutSpecs Are Regenerated @@ -81,11 +81,11 @@ Using `.cornerRadius` will visually degraded performance on iPhone 4, 4S, and 5 For a longer discussion and easy alternative corner rounding solutions, please read our comprehensive corner rounding guide.
    -### AsyncDisplayKit does not support UIKit Auto Layout or InterfaceBuilder +### Texture does not support UIKit Auto Layout or InterfaceBuilder
    -UIKit Auto Layout and InterfaceBuilder are not supported by AsyncDisplayKit. It is worth noting that both of these technologies are not permitted in established and disciplined iOS development teams, such as at Facebook, Instagram, and Pinterest. +UIKit Auto Layout and InterfaceBuilder are not supported by Texture. It is worth noting that both of these technologies are not permitted in established and disciplined iOS development teams, such as at Facebook, Instagram, and Pinterest. -However, AsyncDisplayKit's Layout API provides a variety of ASLayoutSpec objects that allow implementing automatic layout which is more efficient (multithreaded, off the main thread), easier to debug (can step into the code and see where all values come from, as it is open source), and reusable (you can build composable layouts that can be shared with different parts of the UI). +However, Texture's Layout API provides a variety of ASLayoutSpec objects that allow implementing automatic layout which is more efficient (multithreaded, off the main thread), easier to debug (can step into the code and see where all values come from, as it is open source), and reusable (you can build composable layouts that can be shared with different parts of the UI).
    ### ASDisplayNode keep alive reference @@ -118,7 +118,7 @@ Good application design should not rely on this behavior, because a strong refer ### UICollectionViewCell Compatibility -ASDK supports using UICollectionViewCells alongside native ASCellNodes. +Texture supports using UICollectionViewCells alongside native ASCellNodes. Note that these UIKit cells will **not** have the performance benefits of `ASCellNodes` (like preloading, async layout, and async drawing), even when mixed within the same `ASCollectionNode`. diff --git a/docs/_docs/getting-started.md b/docs/_docs/getting-started.md index 4ed58e757..8b11e57cf 100755 --- a/docs/_docs/getting-started.md +++ b/docs/_docs/getting-started.md @@ -5,7 +5,7 @@ permalink: /docs/getting-started.html nextPage: resources.html --- -AsyncDisplayKit's basic unit is the `node`. `ASDisplayNode` is an abstraction +Texture's basic unit is the `node`. `ASDisplayNode` is an abstraction over `UIView`, which in turn is an abstraction over `CALayer`. Unlike views, which can only be used on the main thread, nodes are thread-safe: you can instantiate and configure entire hierarchies of them in parallel on background @@ -17,9 +17,9 @@ has one-sixtieth of a second to push each frame. That's 16 milliseconds to execute all layout and drawing code! And because of system overhead, your code usually has less than ten milliseconds to run before it causes a frame drop. -AsyncDisplayKit lets you move image decoding, text sizing and rendering, and +Texture lets you move image decoding, text sizing and rendering, and other expensive UI operations off the main thread, to keep the main thread available to -respond to user interaction. AsyncDisplayKit has other tricks up its +respond to user interaction. Texture has other tricks up its sleeve too... but we'll get to that later.

    Nodes

    @@ -28,26 +28,26 @@ If you're used to working with views, you already know how to use nodes. Most m Of course, you can always access the underlying view or layer directly via `node.view` or `node.layer`, just make sure to do it on the main thread! -AsyncDisplayKit offers a variety of nodes to replace the majority of the UIKit components that you are used to. Large scale apps have been able to completely write their UI using just AsyncDisplayKit nodes. +Texture offers a variety of nodes to replace the majority of the UIKit components that you are used to. Large scale apps have been able to completely write their UI using just Texture nodes.

    Node Containers

    -When converting an app to use AsyncDisplayKit, a common mistake is to add nodes directly to an existing view hierarchy. Doing this will virtually guarantee that your nodes will flash as they are rendered. +When converting an app to use Texture, a common mistake is to add nodes directly to an existing view hierarchy. Doing this will virtually guarantee that your nodes will flash as they are rendered. -Instead, you should add nodes as subnodes of one of the many node container classes. These containers are in charge of telling contained nodes what state they're currently in so that data can be loaded and nodes can be rendered as efficiently as possible. You should think of these classes as the integration point between UIKit and ASDK. +Instead, you should add nodes as subnodes of one of the many node container classes. These containers are in charge of telling contained nodes what state they're currently in so that data can be loaded and nodes can be rendered as efficiently as possible. You should think of these classes as the integration point between UIKit and Texture.

    Layout Engine

    -AsyncDisplayKit's layout engine is both one of its most powerful and one of its most unique features. Based on the CSS FlexBox model, it provides a declarative way of specifying a custom node's size and layout of its subnodes. While all nodes are concurrently rendered by default, asynchronous measurement and layout are performed by providing an `ASLayoutSpec` for each node. +Texture's layout engine is both one of its most powerful and one of its most unique features. Based on the CSS FlexBox model, it provides a declarative way of specifying a custom node's size and layout of its subnodes. While all nodes are concurrently rendered by default, asynchronous measurement and layout are performed by providing an `ASLayoutSpec` for each node.

    Advanced Developer Features

    -AsyncDisplayKit offers a variety of advanced developer features that cannot be found in UIKit or Foundation. Our developers have found that AsyncDisplyKit allows simplifications in their architecture and improves developer velocity. +Texture offers a variety of advanced developer features that cannot be found in UIKit or Foundation. Our developers have found that AsyncDisplyKit allows simplifications in their architecture and improves developer velocity. (Full list coming soon!) -

    Adding AsyncDisplayKit to your App

    +

    Adding Texture to your App

    -If you are new to AsyncDisplayKit, we recommend that you check out our ASDKgram example app. We've created a handy guide (coming soon!) with step-by-step directions and a follow along example on how to add AsyncDisplayKit to an app. +If you are new to Texture, we recommend that you check out our ASDKgram example app. We've created a handy guide (coming soon!) with step-by-step directions and a follow along example on how to add Texture to an app. -If you run into any problems along the way, reach out to us GitHub or the AsyncDisplayKit Slack community for help. +If you run into any problems along the way, reach out to us GitHub or the Texture Slack community for help. diff --git a/docs/_docs/hit-test-slop.md b/docs/_docs/hit-test-slop.md index 157d7ae5d..fa126ce88 100755 --- a/docs/_docs/hit-test-slop.md +++ b/docs/_docs/hit-test-slop.md @@ -8,7 +8,7 @@ nextPage: batch-fetching-api.html `ASDisplayNode` has a `hitTestSlop` property of type `UIEdgeInsets` that when set to a non-zero inset, increase the bounds for hit testing to make it easier to tap or perform gestures on this node. -ASDisplayNode is the base class for all nodes, so this property is available on any of AsyncDisplayKit's nodes. +ASDisplayNode is the base class for all nodes, so this property is available on any of Texture's nodes.
    Note: This affects the default implementation of -hitTest and -pointInside, so subclasses should call super if you override it and want hitTestSlop applied. diff --git a/docs/_docs/image-node.md b/docs/_docs/image-node.md index 77b2bdd5c..4067aba04 100755 --- a/docs/_docs/image-node.md +++ b/docs/_docs/image-node.md @@ -6,7 +6,7 @@ prevPage: text-node.html nextPage: network-image-node.html --- -`ASImageNode` is the ASDK equivalent to `UIImageView`. The most basic difference is that images are decoded asynchronously by default. Of course, there are more advanced improvments as well such as GIF support and `imageModificationBlock`s. +`ASImageNode` is the Texture equivalent to `UIImageView`. The most basic difference is that images are decoded asynchronously by default. Of course, there are more advanced improvments as well such as GIF support and `imageModificationBlock`s. ### Basic Usage diff --git a/docs/_docs/installation.md b/docs/_docs/installation.md index 10f39e8bd..69b995d75 100755 --- a/docs/_docs/installation.md +++ b/docs/_docs/installation.md @@ -6,7 +6,7 @@ prevPage: resources.html nextPage: adoption-guide-2-0-beta1.html --- -AsyncDisplayKit may be added to your project via CocoaPods or Carthage. Do not forget to import the framework header: +Texture may be added to your project via CocoaPods or Carthage. Do not forget to import the framework header:
    @@ -16,17 +16,17 @@ AsyncDisplayKit may be added to your project via CocoaPods or Carthage. Do not f
    -or create a Objective-C bridging header (Swift). If you have any problems installing AsyncDisplayKit, please contact us on Github or Slack! +or create a Objective-C bridging header (Swift). If you have any problems installing Texture, please contact us on Github or Slack! ## CocoaPods -AsyncDisplayKit is available on CocoaPods. Add the following to your Podfile: +Texture is available on CocoaPods. Add the following to your Podfile: 
     target 'MyApp' do
-	pod "AsyncDisplayKit"
+	pod "Texture"
 end
    @@ -44,12 +44,12 @@ Quit Xcode completely before running in the project directory in Terminal. -To update your version of AsyncDisplayKit, run +To update your version of Texture, run 
    -> pod update AsyncDisplayKit
+> pod update Texture
    @@ -64,14 +64,14 @@ Don't forget to use the workspace `.xcworkspace` file, _not_ the project `.xcode The standard way to use Carthage is to have a Cartfile list the dependencies, and then run `carthage update` to download the dependenices into the `Cathage/Checkouts` folder and build each of those into frameworks located in the `Carthage/Build` folder, and finally the developer has to manually integrate in the project.
    -AsyncDisplayKit is also available through Carthage. +Texture is also available through Carthage. Add the following to your Cartfile to get the **latest release** branch: 
    -github "facebook/AsyncDisplayKit"
+github "texturegroup/texture"
    @@ -82,13 +82,13 @@ Or, to get the **master** branch: 
    -github "facebook/AsyncDisplayKit" "master"
+github "facetexturegroup/textureaster"

    -AsyncDisplayKit has its own Cartfile which lists its dependencies, so this is the only line you will need to include in your Cartfile. +Texture has its own Cartfile which lists its dependencies, so this is the only line you will need to include in your Cartfile. Run @@ -103,12 +103,12 @@ Run
    in Terminal. This will fetch dependencies into a `Carthage/Checkouts` folder, then build each one. -Look for terminal output confirming `AsyncDisplayKit`, `PINRemoteImage (3.0.0-beta.2)` and `PINCache` are all fetched and built. The ASDK framework Cartfile should handle the dependencies correctly. +Look for terminal output confirming `Texture`, `PINRemoteImage (3.0.0-beta.2)` and `PINCache` are all fetched and built. The Texture framework Cartfile should handle the dependencies correctly. In Xcode, on your application targets’ **“General”** settings tab, in the **“Linked Frameworks and Libraries”** section, drag and drop each framework you want to use from the `Carthage/Build` folder on disk. ## Carthage (light) -AsyncDisplayKit does not yet support the lighter way of using Carthage, in which you manually add the project files. This is because one of its dependencies, `PINCache` (a nested dependency of `PINRemoteImage`) does not yet have a project file. +Texture does not yet support the lighter way of using Carthage, in which you manually add the project files. This is because one of its dependencies, `PINCache` (a nested dependency of `PINRemoteImage`) does not yet have a project file. -Without including `PINRemoteImage` and `PINCache`, you will not get AsyncDisplayKit's full image feature set. +Without including `PINRemoteImage` and `PINCache`, you will not get Texture's full image feature set. diff --git a/docs/_docs/intelligent-preloading.md b/docs/_docs/intelligent-preloading.md index e5353a594..24440f1ac 100755 --- a/docs/_docs/intelligent-preloading.md +++ b/docs/_docs/intelligent-preloading.md @@ -6,7 +6,7 @@ prevPage: upgrading.html nextPage: containers-overview.html --- -While a node's ability to be rendered and measured asynchronously and concurrently makes it quite powerful, another crucially important layer to ASDK is the idea of intelligent preloading. +While a node's ability to be rendered and measured asynchronously and concurrently makes it quite powerful, another crucially important layer to Texture is the idea of intelligent preloading. As was pointed out in Getting Started, it is rarely advantageous to use a node outside of the context of one of the node containers. This is due to the fact that all nodes have a notion of their current interface state. diff --git a/docs/_docs/inversion.md b/docs/_docs/inversion.md index d28edb1e9..2231c20b9 100755 --- a/docs/_docs/inversion.md +++ b/docs/_docs/inversion.md @@ -6,7 +6,7 @@ prevPage: automatic-subnode-mgmt.html nextPage: image-modification-block.html --- -`ASTableNode` and `ASCollectionNode` have a `inverted` property of type `BOOL` that when set to `YES`, will automatically invert the content so that it's layed out bottom to top, that is the 'first' (indexPath 0, 0) node is at the bottom rather than the top as usual. This is extremely covenient for chat/messaging apps, and with AsyncDisplayKit it only takes one property. +`ASTableNode` and `ASCollectionNode` have a `inverted` property of type `BOOL` that when set to `YES`, will automatically invert the content so that it's layed out bottom to top, that is the 'first' (indexPath 0, 0) node is at the bottom rather than the top as usual. This is extremely covenient for chat/messaging apps, and with Texture it only takes one property. When this is enabled, developers only have to take one more step to have full inversion support and that is to adjust the `contentInset` of their `ASTableNode` or `ASCollectionNode` like so: @@ -29,4 +29,4 @@ When this is enabled, developers only have to take one more step to have full in
    -See the SocialAppLayout-Inverted example project for more details. +See the SocialAppLayout-Inverted example project for more details. diff --git a/docs/_docs/layer-backing.md b/docs/_docs/layer-backing.md index d02a65f94..3c1b1ca70 100755 --- a/docs/_docs/layer-backing.md +++ b/docs/_docs/layer-backing.md @@ -10,7 +10,7 @@ In some cases, you can substantially improve your app's performance by using lay With UIKit, manually converting view-based code to layers is laborious due to the difference in APIs. Worse, if at some point you need to enable touch handling or other view-specific functionality, you have to manually convert everything back (and risk regressions!). -With all AsyncDisplayKit nodes, converting an entire subtree from views to layers is as simple as: +With all Texture nodes, converting an entire subtree from views to layers is as simple as:
    SwiftObjective-C diff --git a/docs/_docs/layout-api-debugging.md b/docs/_docs/layout-api-debugging.md index 495098d7c..5b8601257 100755 --- a/docs/_docs/layout-api-debugging.md +++ b/docs/_docs/layout-api-debugging.md @@ -12,8 +12,8 @@ Here are some helpful questions to ask yourself when you encounter any issues co
    Certain `ASLayoutable` properties will _only_ apply when the layoutable is a child of a _stack_ spec (the child is called an ASStackLayoutable), while other properties _only_ apply when the layoutable is a child of a _static_ spec (the child is called an ASStaticLayoutable). -- table of [`ASStackLayoutables` properties](http://asyncdisplaykit.org/docs/automatic-layout-containers.html#asstacklayoutable-properties) -- table of [`ASStaticLayoutable` properties](http://asyncdisplaykit.org/docs/automatic-layout-containers.html#asstaticlayoutable-properties) +- table of [`ASStackLayoutables` properties](http://texturegroup.org/docs/automatic-layout-containers.html#asstacklayoutable-properties) +- table of [`ASStaticLayoutable` properties](http://texturegroup.org/docs/automatic-layout-containers.html#asstaticlayoutable-properties) All ASLayoutable properties can be applied to _any_ layoutable (e.g. any node or layout spec), however certain properties will only take effect depending on the type of the parent layout spec they are wrapped in. @@ -25,7 +25,7 @@ A common examples of this confusion involves flex grow and flex shrink. E.g. a n ## Have I provided sizes for any node that lacks an intrinsic size?
    -AsyncDisplayKit's layout pass is recursive, starting at the layout spec returned from `-layoutSpecThatFits:` and proceeding down until it reaches the leaf nodes included in any nested layout specs. +Texture's layout pass is recursive, starting at the layout spec returned from `-layoutSpecThatFits:` and proceeding down until it reaches the leaf nodes included in any nested layout specs. Some leaf nodes have a concept of their own intrinsic size, such as ASTextNode or ASImageNode. A text node knows the length of its formatted string and an ASImageNode knows the size of its static image. Other leaf nodes require an intrinsic size to be set. @@ -49,11 +49,11 @@ Set `.preferredFrameSize` to set a size for any node. Note that setting .preferr Set `.sizeRange` to set a size range for any node or layout spec that is the child of a *static* spec consisting. `.sizeRange` is the *only* way to set a size on a layout spec. Again, when using `.sizeRange`, you *must wrap the layoutable in a static layout spec for it to take effect.* -A `.sizeRange` consists of a minimum and maximum constrained size (these sizes can be a specific point value or a relative value, like 70%). For details on the `.sizeRange` property's custom value type, check out our [Layout API Sizing guide](http://asyncdisplaykit.org/docs/layout-api-sizing.html). +A `.sizeRange` consists of a minimum and maximum constrained size (these sizes can be a specific point value or a relative value, like 70%). For details on the `.sizeRange` property's custom value type, check out our [Layout API Sizing guide](http://texturegroup.org/docs/layout-api-sizing.html). ## `ASRelativeDimension` vs `ASRelativeSize` vs `ASRelativeSizeRange` vs `ASSizeRange`
    -AsyncDisplayKit's Layout API supports configuring node and layout spec sizes with specific point values as well as relative values. Read the [Layout API Sizing guide](http://asyncdisplaykit.org/docs/layout-api-sizing.html) for a helpful chart and documentation on our custom layout value types. +Texture's Layout API supports configuring node and layout spec sizes with specific point values as well as relative values. Read the [Layout API Sizing guide](http://texturegroup.org/docs/layout-api-sizing.html) for a helpful chart and documentation on our custom layout value types. ## Debugging layout specs with ASCII art
    diff --git a/docs/_docs/layout-engine.md b/docs/_docs/layout-engine.md index 79af87a44..f73bed322 100755 --- a/docs/_docs/layout-engine.md +++ b/docs/_docs/layout-engine.md @@ -6,7 +6,7 @@ prevPage: subclassing.html nextPage: containers-overview.html --- -AsyncDisplayKit's layout engine is based on the CSS Box Model. While it is the feature of the framework that bears the weakest resemblance to the UIKit equivalent (AutoLayout), it is also among the most useful features once you've gotten used to it. With enough practice, you may just come to prefer creating declarative layouts to the constraint based approach. ;] +Texture's layout engine is based on the CSS Box Model. While it is the feature of the framework that bears the weakest resemblance to the UIKit equivalent (AutoLayout), it is also among the most useful features once you've gotten used to it. With enough practice, you may just come to prefer creating declarative layouts to the constraint based approach. ;] The main way you participate in this system is by implementing `-layoutSpecThatFits:` in a node subclass. Here, you declaratively build up layout specs from the inside out, returning the final spec which will contain the rest. diff --git a/docs/_docs/layout-options.md b/docs/_docs/layout-options.md index cdefd2a6f..709a7f8be 100755 --- a/docs/_docs/layout-options.md +++ b/docs/_docs/layout-options.md @@ -6,10 +6,10 @@ prevPage: automatic-layout-debugging.html nextPage: layer-backing.html --- -When using ASDK, you have three options for layout. Note that UIKit Autolayout is **not** supported by ASDK. +When using Texture, you have three options for layout. Note that UIKit Autolayout is **not** supported by Texture. #Manual Sizing & Layout -This original layout method shipped with ASDK 1.0 and is analogous to UIKit's layout methods. Use this method for ASViewControllers (unless you subclass the node). +This original layout method shipped with Texture 1.0 and is analogous to UIKit's layout methods. Use this method for ASViewControllers (unless you subclass the node). `[ASDisplayNode calculateSizeThatFits:]` **vs.** `[UIView sizeThatFits:]` diff --git a/docs/_docs/layout-transition-api.md b/docs/_docs/layout-transition-api.md index 1af89390d..02ba1bbef 100755 --- a/docs/_docs/layout-transition-api.md +++ b/docs/_docs/layout-transition-api.md @@ -6,9 +6,9 @@ prevPage: layout2-api-sizing.html nextPage: hit-test-slop.html --- -The Layout Transition API was designed to make all animations with AsyncDisplayKit easy - even transforming an entire set of views into a completely different set of views! +The Layout Transition API was designed to make all animations with Texture easy - even transforming an entire set of views into a completely different set of views! -With this system, you simply specify the desired layout and AsyncDisplayKit will do the work to figure out differences from the current layout. It will automatically add new elements, remove unneeded elements after the transiton, and update the position of any existing elements. +With this system, you simply specify the desired layout and Texture will do the work to figure out differences from the current layout. It will automatically add new elements, remove unneeded elements after the transiton, and update the position of any existing elements. There are also easy to use APIs that allow you to fully customize the starting position of newly introduced elements, as well as the ending position of removed elements. @@ -184,11 +184,11 @@ override func animateLayoutTransition(_ context: ASContextTransitioning) {
    -The passed `ASContextTransitioning` context object in this method contains relevant information to help you determine the state of the nodes before and after the transition. It includes getters into old and new constrained sizes, inserted and removed nodes, and even the raw old and new `ASLayout` objects. In the `SignupNode` example, we're using it to determine the frame for each of the fields and animate them in an out of place. +The passed `ASContextTransitioning` context object in this method contains relevant information to help you determine the state of the nodes before and after the transition. It includes getters into old and new constrained sizes, inserted and removed nodes, and even the raw old and new `ASLayout` objects. In the `SignupNode` example, we're using it to determine the frame for each of the fields and animate them in an out of place. It is imperative to call `completeTransition:` on the context object once your animation has finished, as it will perform the necessary internal steps for the newly calculated layout to become the current `calculatedLayout`. -Note that there hasn't been a use of `addSubnode:` or `removeFromSupernode` during the transition. AsyncDisplayKit's layout transition API analyzes the differences in the node hierarchy between the old and new layout, implicitly performing node insertions and removals via Automatic Subnode Management. +Note that there hasn't been a use of `addSubnode:` or `removeFromSupernode` during the transition. Texture's layout transition API analyzes the differences in the node hierarchy between the old and new layout, implicitly performing node insertions and removals via Automatic Subnode Management. Nodes are inserted before your implementation of `animateLayoutTransition:` is called and this is a good place to manually manage the hierarchy before you begin the animation. Removals are performed in `didCompleteLayoutTransition:` after you call `completeTransition:` on the context object. If you need to manually perform deletions, override `didCompleteLayoutTransition:` and perform your custom operations. Note that this will override the default behavior and it is recommended to either call `super` or walk through the `removedSubnodes` getter in the context object to perform the cleanup. @@ -256,4 +256,4 @@ override func viewWillTransition(to size: CGSize, with coordinator: UIViewContro ## Examples that use the Layout Transition API -- [ASDKLayoutTransition](https://github.com/facebook/AsyncDisplayKit/tree/master/examples/ASDKLayoutTransition) +- [ASDKLayoutTransition](https://github.com/texturegroup/texture/tree/master/examples/ASDKLayoutTransition) diff --git a/docs/_docs/layout2-conversion-guide.md b/docs/_docs/layout2-conversion-guide.md index 564f2778a..6283cf1ec 100755 --- a/docs/_docs/layout2-conversion-guide.md +++ b/docs/_docs/layout2-conversion-guide.md @@ -19,7 +19,7 @@ A list of the changes: - Rename `ASRelativeDimension` to `ASDimension` - Introduction of `ASDimensionUnitAuto` -In addition to the inline examples comparing **1.x** layout code vs **2.0** layout code, the [example projects](https://github.com/facebook/AsyncDisplayKit/tree/master/examples) and layout documentation have been updated to use the new API. +In addition to the inline examples comparing **1.x** layout code vs **2.0** layout code, the [example projects](https://github.com/texturegroup/texture/tree/master/examples) and layout documentation have been updated to use the new API. All other **2.0** changes not related to the Layout API are documented here. @@ -390,7 +390,7 @@ In certain advanced cases, you may want to override this method. Overriding this Call this on children`layoutElements` to compute their layouts within your implementation of `-calculateLayoutThatFits:`. -For sample implementations of layout specs and the usage of the `calculateLayoutThatFits:` family of methods, check out the layout specs in AsyncDisplayKit itself! +For sample implementations of layout specs and the usage of the `calculateLayoutThatFits:` family of methods, check out the layout specs in Texture itself! ## Deprecation of `-[ASDisplayNode measure:]` @@ -458,7 +458,7 @@ Due to the removal of `-[ASAbsoluteLayoutElement sizeRange]`, we also removed th ## Rename `ASRelativeDimension` to `ASDimension` -To simplify the naming and support the fact that dimensions are widely used in ASDK now, `ASRelativeDimension` was renamed to `ASDimension`. Having a shorter name and handy functions to create it was an important goal for us. +To simplify the naming and support the fact that dimensions are widely used in Texture now, `ASRelativeDimension` was renamed to `ASDimension`. Having a shorter name and handy functions to create it was an important goal for us. `ASRelativeDimensionTypePercent` and associated functions were renamed to use `Fraction` to be consistent with Apple terminology. diff --git a/docs/_docs/layout2-layoutspec-types.md b/docs/_docs/layout2-layoutspec-types.md index f5ac3ea75..5c753bd49 100755 --- a/docs/_docs/layout2-layoutspec-types.md +++ b/docs/_docs/layout2-layoutspec-types.md @@ -70,7 +70,7 @@ override func layoutSpecThatFits(_ constrainedSize: ASSizeRange) -> ASLayoutSpec ## ASStackLayoutSpec (Flexbox Container) -Of all the layoutSpecs in ASDK, `ASStackLayoutSpec` is the most useful and powerful. `ASStackLayoutSpec` uses the flexbox algorithm to determine the position and size of its children. Flexbox is designed to provide a consistent layout on different screen sizes. In a stack layout you align items in either a vertical or horizontal stack. A stack layout can be a child of another stack layout, which makes it possible to create almost any layout using a stack layout spec. +Of all the layoutSpecs in Texture, `ASStackLayoutSpec` is the most useful and powerful. `ASStackLayoutSpec` uses the flexbox algorithm to determine the position and size of its children. Flexbox is designed to provide a consistent layout on different screen sizes. In a stack layout you align items in either a vertical or horizontal stack. A stack layout can be a child of another stack layout, which makes it possible to create almost any layout using a stack layout spec. `ASStackLayoutSpec` has 7 properties in addition to its `` properties: @@ -131,7 +131,7 @@ override func layoutSpecThatFits(_ constrainedSize: ASSizeRange) -> ASLayoutSpec -Flexbox works the same way in AsyncDisplayKit as it does in CSS on the web, with a few exceptions. For example, the defaults are different and there is no `flex` parameter. See Web Flexbox Differences for more information. +Flexbox works the same way in Texture as it does in CSS on the web, with a few exceptions. For example, the defaults are different and there is no `flex` parameter. See Web Flexbox Differences for more information.
    diff --git a/docs/_docs/layout2-manual-layout.md b/docs/_docs/layout2-manual-layout.md index 2d4a16ceb..fef0ccf50 100755 --- a/docs/_docs/layout2-manual-layout.md +++ b/docs/_docs/layout2-manual-layout.md @@ -5,7 +5,7 @@ permalink: /docs/layout2-manual-layout.html --- ## Manual Layout -After diving in to the automatic way for layout in ASDK there is still the _old_ way to layout manually available. For the sake of completness here is a short description how to accomplish that within ASDK. +After diving in to the automatic way for layout in Texture there is still the _old_ way to layout manually available. For the sake of completness here is a short description how to accomplish that within Texture. ### Manual Layout UIKit @@ -68,9 +68,9 @@ Further, even with a cache, we'll still be blocking the main thread on sizing *s This is a pretty deep rabbit hole. We could attempt to work around the fact that UILabels and UITextViews cannot safely be sized on background threads by manually creating a TextKit stack and sizing the text ourselves... but that's a laborious duplication of work. Further, if UITextView's layout behaviour changes in an iOS update, our sizing code will break. (And did we mention that TextKit isn't thread-safe either?) -### Manual Layout ASDK +### Manual Layout Texture -Manual layout within ASDK are realized within two methods: +Manual layout within Texture are realized within two methods: #### `calculateSizeThatFits` and `layout` @@ -161,7 +161,7 @@ Our custom node looks like this: -`ASImageNode` and `ASTextNode`, like the rest of AsyncDisplayKit, are thread-safe, so we can size them on background threads. The `-layoutThatFits:` method is like `-sizeThatFits:`, but with side effects: it caches the (`calculatedSize`) for quick access later on — like in our now-snappy `-layout` implementation. +`ASImageNode` and `ASTextNode`, like the rest of Texture, are thread-safe, so we can size them on background threads. The `-layoutThatFits:` method is like `-sizeThatFits:`, but with side effects: it caches the (`calculatedSize`) for quick access later on — like in our now-snappy `-layout` implementation. As you can see, node hierarchies are sized and laid out in much the same way as their view counterparts. Manually layed out nodes do need to be written with a few things in mind: diff --git a/docs/_docs/layout2-quickstart.md b/docs/_docs/layout2-quickstart.md index 96c7726ee..798e0a2ec 100755 --- a/docs/_docs/layout2-quickstart.md +++ b/docs/_docs/layout2-quickstart.md @@ -8,7 +8,7 @@ nextPage: automatic-layout-examples-2.html ## Motivation & Benefits -The Layout API was created as a performant alternative to UIKit's Auto Layout, which becomes exponentially expensive for complicated view hierarchies. AsyncDisplayKit's Layout API has many benefits over using UIKit's Auto Layout: +The Layout API was created as a performant alternative to UIKit's Auto Layout, which becomes exponentially expensive for complicated view hierarchies. Texture's Layout API has many benefits over using UIKit's Auto Layout: - **Fast**: As fast as manual layout code and significantly faster than Auto Layout - **Asynchronous & Concurrent:** Layouts can be computed on background threads so user interactions are not interrupted. @@ -18,11 +18,11 @@ The Layout API was created as a performant alternative to UIKit's Auto Layout, w ## Inspired by CSS Flexbox -Those who are familiar with Flexbox will notice many similarities in the two systems. However, AsyncDisplayKit's Layout API does not re-implement all of CSS. +Those who are familiar with Flexbox will notice many similarities in the two systems. However, Texture's Layout API does not re-implement all of CSS. ## Basic Concepts -AsyncDisplayKit's layout system is centered around two basic concepts: +Texture's layout system is centered around two basic concepts: 1. Layout Specs 2. Layout Elements @@ -32,7 +32,7 @@ AsyncDisplayKit's layout system is centered around two basic concepts: A layout spec, short for "layout specification", has no physical presence. Instead, layout specs act as containers for other layout elements by understanding how these children layout elements relate to each other. -AsyncDisplayKit provides several subclasses of `ASLayoutSpec`, from a simple layout specification that insets a single child, to a more complex layout specification that arranges multiple children in varying stack configurations. +Texture provides several subclasses of `ASLayoutSpec`, from a simple layout specification that insets a single child, to a more complex layout specification that arranges multiple children in varying stack configurations. ### Layout Elements @@ -54,7 +54,7 @@ The play button on top of the `ASVideoNode` (top image) is placed using an `ASCe ### Some nodes need Sizes Set - + Some elements have an "intrinsic size" based on their immediately available content. For example, ASTextNode can calculate its size based on its attributed string. Other nodes that have an intrinsic size include diff --git a/docs/_docs/layout2-web-flexbox-differences.md b/docs/_docs/layout2-web-flexbox-differences.md index d31285e22..73dac79fe 100755 --- a/docs/_docs/layout2-web-flexbox-differences.md +++ b/docs/_docs/layout2-web-flexbox-differences.md @@ -4,7 +4,7 @@ layout: docs permalink: /docs/layout2-web-flexbox-differences.html --- -The goal of AsyncDisplayKit's Layout API is *not* to re-implement all of CSS. It only targets a subset of CSS and Flexbox container, and there are no plans to implement support for tables, floats, or any other CSS concepts. The AsyncDisplayKit Layout API also does not plan to support styling properties which do not affect layout such as color or background properties. +The goal of Texture's Layout API is *not* to re-implement all of CSS. It only targets a subset of CSS and Flexbox container, and there are no plans to implement support for tables, floats, or any other CSS concepts. The Texture Layout API also does not plan to support styling properties which do not affect layout such as color or background properties. The layout system tries to stay as close as possible to CSS. There are, however, certain cases where it differs from the web, these include: diff --git a/docs/_docs/node-overview.md b/docs/_docs/node-overview.md index 4b0a5182b..6f3b4ca1a 100755 --- a/docs/_docs/node-overview.md +++ b/docs/_docs/node-overview.md @@ -6,19 +6,19 @@ prevPage: containers-overview.html nextPage: subclassing.html --- -AsyncDisplayKit offers the following nodes. +Texture offers the following nodes. A key advantage of using nodes over UIKit components is that **all nodes preform layout and display off of the main thread**, so that the main thread is available to immediately respond to user interaction events.
    ASDK Node ContainerTexture Node Container UIKit Equivalent
    - + + The root Texture node, from which all other nodes inherit. @@ -63,14 +63,14 @@ A key advantage of using nodes over UIKit components is that **all nodes preform
    ASDK NodeTexture Node UIKit Equivalent
    ASDisplayNode in place of UIKit's UIView
    - The root AsyncDisplayKit node, from which all other nodes inherit.
    ASCellNode

    -Despite having rough equivalencies to UIKit components, in general, AsyncDisplayKit nodes offer more advanced features and conveniences. For example, an `ASNetworkImageNode` does automatic loading and cache management, and even supports progressive jpeg and animated gifs. +Despite having rough equivalencies to UIKit components, in general, Texture nodes offer more advanced features and conveniences. For example, an `ASNetworkImageNode` does automatic loading and cache management, and even supports progressive jpeg and animated gifs. -The `AsyncDisplayKitOverview` example app gives basic implementations of each of the nodes listed above. +The `AsyncDisplayKitOverview` example app gives basic implementations of each of the nodes listed above. # Node Inheritance Hierarchy -All AsyncDisplayKit nodes inherit from `ASDisplayNode`. +All Texture nodes inherit from `ASDisplayNode`. node inheritance flowchart diff --git a/docs/_docs/philosophy.md b/docs/_docs/philosophy.md index fc16f1a05..48481180a 100755 --- a/docs/_docs/philosophy.md +++ b/docs/_docs/philosophy.md @@ -8,36 +8,36 @@ nextPage: installation.html #Asynchronous Performance Gains -AsyncDisplayKit is a UI framework that was originally born from Facebook’s Paper app. It came as an answer to one of the core questions the Paper team faced. **How can you keep the main thread as clear as possible?** +Texture is a UI framework that was originally born from Facebook’s Paper app. It came as an answer to one of the core questions the Paper team faced. **How can you keep the main thread as clear as possible?** Nowadays, many apps have a user experience that relies heavily upon continuous gestures and physics based animations. At the very least, your UI is probably dependent on some form of scroll view. These types of user interfaces depend entirely on the main thread and are extremely sensitive to main thread stalls. **A clogged main thread means dropped frames and an unpleasant user experience.** -AsyncDisplayKit Nodes are a thread-safe abstraction layer over UIViews and CALayers: +Texture Nodes are a thread-safe abstraction layer over UIViews and CALayers: logo You can access most view and layer properties when using nodes, the difference is that nodes are rendered concurrently by default, and measured and laid out asynchronously when used correctly! -Too see asynchronous performance gains in action, check out the `examples/ASDKgram` app which compares a UIKit-implemented social media feed with an ASDK-implemented social media feed! +Too see asynchronous performance gains in action, check out the `examples/ASDKgram` app which compares a UIKit-implemented social media feed with an Texture-implemented social media feed! -On an iPhone 6+, the performance may not be radically different, but on a 4S, the difference is dramatic! Which leads us to ASDK's next priority... +On an iPhone 6+, the performance may not be radically different, but on a 4S, the difference is dramatic! Which leads us to Texture's next priority... #A Great App Experience for All Users -ASDK's performance gains allow you to easily design a great experience for every app user - across all devices, on all network connections. +Texture's performance gains allow you to easily design a great experience for every app user - across all devices, on all network connections. ##A Great Developer Experience -ASDK also strives to make the developer experience great +Texture also strives to make the developer experience great - platform compatability: iOS & tvOS - language compatability: Objective-C & Swift -- requires fewer lines of code to build advanced apps (see `examples/ASDKgram` for a direct comparison of a UIKit implemention of an app vs. an equivalent ASDK implementation) +- requires fewer lines of code to build advanced apps (see `examples/ASDKgram` for a direct comparison of a UIKit implemention of an app vs. an equivalent Texture implementation) - cleaner architecture patterns - robust code (some really brilliant minds have worked on this for 3+ years). #Advanced Developer Tools -As ASDK has grown, some of the brightest iOS engineers have contributed advanced technologies that will save you, as a developer using ASDK, development time. +As Texture has grown, some of the brightest iOS engineers have contributed advanced technologies that will save you, as a developer using Texture, development time. ###Advanced Technology - ASRunLoopQueue diff --git a/docs/_docs/placeholder-fade-duration.md b/docs/_docs/placeholder-fade-duration.md index f236f6a71..0b5ca8b13 100755 --- a/docs/_docs/placeholder-fade-duration.md +++ b/docs/_docs/placeholder-fade-duration.md @@ -17,9 +17,9 @@ The `-placeholderImage` function may be called on a background thread, so it is
    -An ideal resource for creating placeholder images, including rounded rect solid colored ones or simple square corner ones is the `UIImage+ASConvenience` category methods in ASDK. +An ideal resource for creating placeholder images, including rounded rect solid colored ones or simple square corner ones is the `UIImage+ASConvenience` category methods in Texture. -See our ancient Placeholders sample app to see this concept, first invented by the Facebook Paper team, in action. +See our ancient Placeholders sample app to see this concept, first invented by the Facebook Paper team, in action. ## `.neverShowPlaceholders` diff --git a/docs/_docs/principles.md b/docs/_docs/principles.md index 8815a402d..aec7fb2df 100755 --- a/docs/_docs/principles.md +++ b/docs/_docs/principles.md @@ -4,7 +4,7 @@ layout: docs permalink: /docs/principles.html --- -The following principles guide the design and development of the AsyncDisplayKit framework. +The following principles guide the design and development of the Texture framework. ## 1. Reliable @@ -21,7 +21,7 @@ The following principles guide the design and development of the AsyncDisplayKit ## 3. Lean - **What:** Speed and memory conservation should be industry-leading, the API should be concise, and implementation code should be short and organized. -- **Why:** Performance is at the heart of AsyncDisplayKit. It's what we do and we do it better than anyone else. In addition, a concise codebase and API are easier to maintain and learn. Plus it's just the right thing to do. +- **Why:** Performance is at the heart of Texture. It's what we do and we do it better than anyone else. In addition, a concise codebase and API are easier to maintain and learn. Plus it's just the right thing to do. - **How:** Look for opportunities to improve performance. Think about the performance implications of each line of code. Dedicate resources to refactoring. Build tools to gather and expose performance metrics. ## 4. Bold diff --git a/docs/_docs/resources.md b/docs/_docs/resources.md index 503e556d7..034e99b72 100755 --- a/docs/_docs/resources.md +++ b/docs/_docs/resources.md @@ -8,15 +8,15 @@ nextPage: installation.html ### Slack -Join 700+ AsyncDisplayKit developers and the AsyncDisplayKit core team on Slack for real-time debugging, the latest updates, and asynchronous banter. Signup here. +Join 700+ Texture developers and the Texture core team on Slack for real-time debugging, the latest updates, and asynchronous banter. Signup here. ### Examples -Browse through our many example projects. +Browse through our many example projects. -If you are new to AsyncDisplayKit, we recommend that you start with the ASDKgram example app which compares a photo feed implemented with UIKit to an identical feed implemented with AsyncDisplayKit. The app features: +If you are new to Texture, we recommend that you start with the ASDKgram example app which compares a photo feed implemented with UIKit to an identical feed implemented with Texture. The app features:
      -
    1. An infinitely scrolling home feed that demonstrates ASDK's smoother scrolling performance.
      2. -
    2. A significantly sized code base to demonstrate how much less code it takes to design apps using AsyncDisplayKit.
      3. +
    3. An infinitely scrolling home feed that demonstrates Texture's smoother scrolling performance.
      4. +
    4. A significantly sized code base to demonstrate how much less code it takes to design apps using Texture.
    ### Videos @@ -41,7 +41,7 @@ Smooth Scrolling in Buffer for iOS: How (and Why) We Implemented AsyncDisplayKit ### Layout Resources -AsyncDisplayKit's powerful layout system is based on the CSS FlexBox model. These sites are useful for learning the basics of this system. +Texture's powerful layout system is based on the CSS FlexBox model. These sites are useful for learning the basics of this system.
    • ASStackLayout Game
    • Visual Guide to CSS3 Flexbox
      • diff --git a/docs/_docs/roadmap.md b/docs/_docs/roadmap.md index 569f2126a..2ef087362 100755 --- a/docs/_docs/roadmap.md +++ b/docs/_docs/roadmap.md @@ -4,9 +4,9 @@ layout: docs permalink: /docs/roadmap.html --- -This document outlines some of the upcoming plans for AsyncDisplayKit. Since AsyncDisplayKit is a fast-moving project with a small core team, this roadmap will change over time. +This document outlines some of the upcoming plans for Texture. Since Texture is a fast-moving project with a small core team, this roadmap will change over time. -The AsyncDisplayKit roadmap is driven by the framework's four key qualities. You can read read more about the principles here. +The Texture roadmap is driven by the framework's four key qualities. You can read read more about the principles here. ## 2.1 Release @@ -44,6 +44,6 @@ The AsyncDisplayKit roadmap is driven by the framework's four key qualities. You - Connect on GitHub, Slack and Twitter. - Vet our documentation. Submit or suggest ways to improve. -- Share your experience using AsyncDisplayKit. Thanks Buffer! +- Share your experience using Texture. Thanks Buffer! - Contribute layout examples. - Contribute code. Try to implement one of our "Needs Volunteer" issues. diff --git a/docs/_docs/subtree-rasterization.md b/docs/_docs/subtree-rasterization.md index a086cea31..8671a524f 100755 --- a/docs/_docs/subtree-rasterization.md +++ b/docs/_docs/subtree-rasterization.md @@ -8,7 +8,7 @@ nextPage: synchronous-concurrency.html Flattening an entire view hierarchy into a single layer improves performance, but with UIKit, comes with a hit to maintainability and hierarchy-based reasoning. -With all AsyncDisplayKit nodes, enabling precompositing is as simple as: +With all Texture nodes, enabling precompositing is as simple as:
      SwiftObjective-C diff --git a/docs/_docs/synchronous-concurrency.md b/docs/_docs/synchronous-concurrency.md index e0d9053d2..3d838e3e0 100755 --- a/docs/_docs/synchronous-concurrency.md +++ b/docs/_docs/synchronous-concurrency.md @@ -10,7 +10,7 @@ Both `ASViewController` and `ASCellNode` have a property called `neverShowPlaceh By setting this property to YES, the main thread will be blocked until display has completed for the cell or view controller's view. -Using this option does not eliminate all of the performance advantages of AsyncDisplayKit. Normally, a given node has been preloading and is almost done when it reaches the screen, so the blocking time is very short. Even if the rangeTuningParameters are set to 0 this option outperforms UIKit. While the main thread is waiting, all subnode display executes concurrently, thus synchronous concurrency. +Using this option does not eliminate all of the performance advantages of Texture. Normally, a given node has been preloading and is almost done when it reaches the screen, so the blocking time is very short. Even if the rangeTuningParameters are set to 0 this option outperforms UIKit. While the main thread is waiting, all subnode display executes concurrently, thus synchronous concurrency.
      SwiftObjective-C @@ -25,4 +25,4 @@ node.neverShowPlaceholders = true

      -Usually, if a cell hasn't finished its display pass before it has reached the screen it will show placeholders until it has drawing its content. Setting this option to YES makes your scrolling node or ASViewController act more like UIKit, and in fact makes AsyncDisplayKit scrolling visually indistinguishable from UIKit's, except that it's faster. +Usually, if a cell hasn't finished its display pass before it has reached the screen it will show placeholders until it has drawing its content. Setting this option to YES makes your scrolling node or ASViewController act more like UIKit, and in fact makes Texture scrolling visually indistinguishable from UIKit's, except that it's faster. diff --git a/docs/_docs/team.md b/docs/_docs/team.md index b4351ed8d..307b6a904 100755 --- a/docs/_docs/team.md +++ b/docs/_docs/team.md @@ -7,17 +7,17 @@ permalink: /docs/team.html - +

      Scott is deeply passionate about building Texture into a framework that allows effortless development of polished and performant apps that serve all users, regardless of device age, internet connection, or language.

      - + - + @@ -25,20 +25,20 @@ permalink: /docs/team.html -

      Scott Goodson (@appleguy) is an original author of AsyncDisplayKit and, most recently, a driving force behind making Pinterest's design vision a reality with the recent rewrite of the iOS app.

      +

      Scott Goodson (@appleguy) is an original author of Texture and, most recently, a driving force behind making Pinterest's design vision a reality with the recent rewrite of the iOS app.

      Previously, Scott managed the Facebook Paper and Instagram iOS engineering teams, and helped lead the native code rewrite of the core Facebook iOS app. He also spent four years at Apple where he was one of the first ten engineers to work on iPhone OS 1.0, and developed apps like Stocks and Calculator.

      -

      Scott is deeply passionate about building AsyncDisplayKit into a framework that allows effortless development of polished and performant apps that serve all users, regardless of device age, internet connection, or language.

      Michael Schneider (@maicki) is especially passionate about API design and recently led the re-architecture of the layout API for the 2.0 release. As our resident layout expert, Michael volunteers much of his own time to help developers on ASDK's public slack channel. Previous, Michael worked on Pocket for iOS, Mac and Chrome and the Instapaper Mac app.

      Michael Schneider (@maicki) is especially passionate about API design and recently led the re-architecture of the layout API for the 2.0 release. As our resident layout expert, Michael volunteers much of his own time to help developers on Texture's public slack channel. Previous, Michael worked on Pocket for iOS, Mac and Chrome and the Instapaper Mac app.

      Huy Nguyen (@nguyenhuy ) joined the Pinterest team after authoring AsyncDisplayKit's automatic layout feature, which has become the foundation for the AsyncDisplayKit's 2.0 release. To date, the Layout API has been the largest contribution to the framework by a community member!

      Huy Nguyen (@nguyenhuy ) joined the Pinterest team after authoring Texture's automatic layout feature, which has become the foundation for the Texture's 2.0 release. To date, the Layout API has been the largest contribution to the framework by a community member!

      Adlai ("Ad-lee") Holler (@adlai-holler) joined the Pinterest team after making major contributions to the framework while writing Tripstr in Swift with AsyncDisplayKit.

      +

      Adlai ("Ad-lee") Holler (@adlai-holler) joined the Pinterest team after making major contributions to the framework while writing Tripstr in Swift with Texture.
      # Join us! -We are looking for senior developers familiar with AsyncDisplayKit to join our team! +We are looking for senior developers familiar with Texture to join our team! We have an exciting roadmap that we believe will continue to push the boundaries of what is possible on the iOS platform, while making the framework easier to use than ever before. -As part of the team, you would work on AsyncDisplayKit, [PINRemoteImage](https://github.com/pinterest/PINRemoteImage), and [PINCache](https://github.com/pinterest/PINCache) (the backing store for ASNetworkImageNode), while using all three in Pinterest's [app](https://itunes.apple.com/us/app/pinterest/id429047995). +As part of the team, you would work on Texture, [PINRemoteImage](https://github.com/pinterest/PINRemoteImage), and [PINCache](https://github.com/pinterest/PINCache) (the backing store for ASNetworkImageNode), while using all three in Pinterest's [app](https://itunes.apple.com/us/app/pinterest/id429047995). -One interesting thing to note is that Pinterest does not have an internal fork of AsyncDisplayKit. Everything is developed on master, with release branches cut from master only a few weeks before our public application launches. This allows us to move exceptionally quickly in developing and launching improvements to millions of users. +One interesting thing to note is that Pinterest does not have an internal fork of Texture. Everything is developed on master, with release branches cut from master only a few weeks before our public application launches. This allows us to move exceptionally quickly in developing and launching improvements to millions of users. Sound interesting? -Send us an email at AsyncDisplayKit(at)gmail.com. +Send us an email at textureframework@gmail.com. diff --git a/docs/_docs/text-node.md b/docs/_docs/text-node.md index 24b1fbaed..b2774fac1 100755 --- a/docs/_docs/text-node.md +++ b/docs/_docs/text-node.md @@ -6,7 +6,7 @@ prevPage: button-node.html nextPage: image-node.html --- -`ASTextNode` is AsyncDisplayKit's main text node and can be used any time you would normally use a `UILabel`. It includes full rich text support and is a subclass of `ASControlNode` meaning it can be used any time you would normally create a UIButton with just its titleLabel set. +`ASTextNode` is Texture's main text node and can be used any time you would normally use a `UILabel`. It includes full rich text support and is a subclass of `ASControlNode` meaning it can be used any time you would normally create a UIButton with just its titleLabel set. ### Basic Usage `ASTextNode`'s interface should be familiar to anyone who's used a `UILabel`. The first difference you may notice, is that text node's only use attributed strings instead of having the option of using a plain string. diff --git a/docs/_docs/tip-1-nodeBlocks.md b/docs/_docs/tip-1-nodeBlocks.md index 5f30316e2..488465f83 100755 --- a/docs/_docs/tip-1-nodeBlocks.md +++ b/docs/_docs/tip-1-nodeBlocks.md @@ -4,7 +4,7 @@ layout: docs permalink: /docs/tip-1-nodeBlocks.html --- -AsyncDisplayKit’s `ASCollectionNode` replaces `UICollectionView`’s required method +Texture’s `ASCollectionNode` replaces `UICollectionView`’s required method
      diff --git a/docs/_docs/uicollectionview-challenges.md b/docs/_docs/uicollectionview-challenges.md index 9f554df24..4916bf3e9 100755 --- a/docs/_docs/uicollectionview-challenges.md +++ b/docs/_docs/uicollectionview-challenges.md @@ -86,7 +86,7 @@ There is no easy, universal way to handle loading content such as:

      Unified Cell Measurement & Allocation

      -AsyncDisplayKit takes both of the important collection methods explained above: +Texture takes both of the important collection methods explained above:
      SwiftObjective-C @@ -138,13 +138,13 @@ func collectionNode(collectionNode: ASCollectionNode, nodeBlockForItemAtIndexPat *Note that there is an optional method to provide a constrained size for the cell, but it is not needed by most apps. -ASCellNode, is AsyncDisplayKit's universal cell class. They are light-weight enough to be created an an earlier time in the program (concurrently in the background) and they understand how to calculate their own size. `ASCellNode` automatically caches its measurement so that it can be quickly applied during the layout pass. +ASCellNode, is Texture's universal cell class. They are light-weight enough to be created an an earlier time in the program (concurrently in the background) and they understand how to calculate their own size. `ASCellNode` automatically caches its measurement so that it can be quickly applied during the layout pass.
      As a comparison to the diagram above, this detailed diagram shows the full process of an ASCollectionView communicating with its data source and delegate to display itself.. Note that ASCollectionView is ASCollectionNode's underlying UICollectionView subclass.
      -

      Benefits of AsyncDisplayKit's Architecture

      +

      Benefits of Texture's Architecture

      Elimination of all of the types of main thread work described above (cell allocation, measurement, layout, display)! In addition, all of this work is preformed concurrently on multiple threads. @@ -153,7 +153,7 @@ Because `ASCollectionNode` is aware of the position of all of its nodes, it can Lastly, almost all of the concepts we've discussed here apply to `UITableView` / `ASTableNode` and `UIPageViewController` / `ASPagerNode`. ## iOS 10 Cell Pre-fetching -Inspired by ASDK, iOS 10 introduced a cell pre-fetching. This API increases the number of cells that the collection tracks at any given time, which helps, but isn't anywhere as performance centric as being aware of all cells in the data source. +Inspired by Texture, iOS 10 introduced a cell pre-fetching. This API increases the number of cells that the collection tracks at any given time, which helps, but isn't anywhere as performance centric as being aware of all cells in the data source. Additionally, iOS9 still constitutes a substantial precentage of most app's userbase and will not reduce in number anywhere close to as quickly as the sunset trajectory of iOS 7 and iOS 8 devices. Whereas iOS 9 is the last supported version for about a half-dozen devices, there were zero devices that were deprecated on iOS 8 and only one deivce deprecated on iOS 7. diff --git a/docs/_docs/uicollectionviewinterop.md b/docs/_docs/uicollectionviewinterop.md index 6f39fa15d..26fc1942e 100755 --- a/docs/_docs/uicollectionviewinterop.md +++ b/docs/_docs/uicollectionviewinterop.md @@ -6,7 +6,7 @@ prevPage: placeholder-fade-duration.html nextPage: accessibility.html --- -AsyncDisplayKit's `ASCollectionNode` offers compatibility with synchronous, standard `UICollectionViewCell` objects alongside native `ASCellNodes`. +Texture's `ASCollectionNode` offers compatibility with synchronous, standard `UICollectionViewCell` objects alongside native `ASCellNodes`. Note that these UIKit cells will **not** have the performance benefits of `ASCellNodes` (like preloading, async layout, and async drawing), even when mixed within the same `ASCollectionNode`. @@ -29,11 +29,11 @@ In order to use this feature, you must: -By default, the interop data source will only be consulted in cases where no `ASCellNode` is provided to AsyncDisplayKit. However, if .dequeuesCellsForNodeBackedItems is enabled, then the interop data source will always be consulted to dequeue cells, and will be expected to return _ASCollectionViewCells in cases where a node was provided. +By default, the interop data source will only be consulted in cases where no `ASCellNode` is provided to Texture. However, if .dequeuesCellsForNodeBackedItems is enabled, then the interop data source will always be consulted to dequeue cells, and will be expected to return _ASCollectionViewCells in cases where a node was provided. ## CustomCollectionView Example App -The [CustomCollectionView](https://github.com/facebook/AsyncDisplayKit/tree/master/examples/CustomCollectionView) example project demonstrates how to use raw `UIKit` cells alongside native `ASCellNodes`. +The [CustomCollectionView](https://github.com/texturegroup/texture/tree/master/examples/CustomCollectionView) example project demonstrates how to use raw `UIKit` cells alongside native `ASCellNodes`. Open the app and verify that `kShowUICollectionViewCells` is enabled in `Sample/ViewController.m`. diff --git a/docs/_includes/header.html b/docs/_includes/header.html index cd54d0a34..78db9b75e 100755 --- a/docs/_includes/header.html +++ b/docs/_includes/header.html @@ -2,7 +2,7 @@ - AsyncDisplayKit | {{ page.title }} + Texture | {{ page.title }} @@ -25,10 +25,10 @@ - - - - + + + + @@ -41,14 +41,14 @@
      -

      AsyncDisplayKit

      +

      Texture

      diff --git a/docs/_includes/hero.html b/docs/_includes/hero.html index d9e64e8c2..e94f6b5f1 100755 --- a/docs/_includes/hero.html +++ b/docs/_includes/hero.html @@ -1,7 +1,7 @@
      -

      AsyncDisplayKit

      +

      Texture

      Get Started
      diff --git a/docs/appledoc/Categories/ASCellNode+.html b/docs/appledoc/Categories/ASCellNode+.html index 8e75aaf5d..23e0e26c2 100755 --- a/docs/appledoc/Categories/ASCellNode+.html +++ b/docs/appledoc/Categories/ASCellNode+.html @@ -18,7 +18,7 @@

      - AsyncDisplayKit + Texture

      @@ -206,7 +206,7 @@

      Declared In

      -

      Copyright © 2016 AsyncDisplayKit. All rights reserved. Updated: 2016-11-05

      +

      Copyright © 2016 Texture. All rights reserved. Updated: 2016-11-05

      Generated by appledoc 2.2.1 (build 1334).

      diff --git a/docs/appledoc/Categories/UIImage+ASDKAdditions.html b/docs/appledoc/Categories/UIImage+ASDKAdditions.html index 72e65a6ad..6bf790311 100755 --- a/docs/appledoc/Categories/UIImage+ASDKAdditions.html +++ b/docs/appledoc/Categories/UIImage+ASDKAdditions.html @@ -18,7 +18,7 @@

      - AsyncDisplayKit + Texture

      @@ -336,7 +336,7 @@

      Declared In

      -

      Copyright © 2016 AsyncDisplayKit. All rights reserved. Updated: 2016-11-05

      +

      Copyright © 2016 Texture. All rights reserved. Updated: 2016-11-05

      Generated by appledoc 2.2.1 (build 1334).

      diff --git a/docs/appledoc/Classes/ASLayoutSpec.html b/docs/appledoc/Classes/ASLayoutSpec.html index 0502e88f3..3bb92fb29 100755 --- a/docs/appledoc/Classes/ASLayoutSpec.html +++ b/docs/appledoc/Classes/ASLayoutSpec.html @@ -18,7 +18,7 @@

      - AsyncDisplayKit + Texture

      @@ -347,7 +347,7 @@

      Declared In

      -

      Copyright © 2016 AsyncDisplayKit. All rights reserved. Updated: 2016-11-05

      +

      Copyright © 2016 Texture. All rights reserved. Updated: 2016-11-05

      Generated by appledoc 2.2.1 (build 1334).

      diff --git a/docs/appledoc/Protocols/ASVisibilityDepth.html b/docs/appledoc/Protocols/ASVisibilityDepth.html index b9e2772ab..29597c887 100755 --- a/docs/appledoc/Protocols/ASVisibilityDepth.html +++ b/docs/appledoc/Protocols/ASVisibilityDepth.html @@ -18,7 +18,7 @@

      - AsyncDisplayKit + Texture

      @@ -99,7 +99,7 @@

      ASVisibilityDepth Protocol Reference

      Overview

      ASVisibilityDepth

      “Visibility Depth” represents the number of user actions required to make an ASDisplayNode or -ASViewController visibile. AsyncDisplayKit uses this information to intelligently manage memory and focus +ASViewController visibile. Texture uses this information to intelligently manage memory and focus resources where they are most visible to the user.

      The ASVisibilityDepth protocol describes how custom view controllers can integrate with this system.

      diff --git a/docs/index.md b/docs/index.md index 5168c91cf..ad660777f 100755 --- a/docs/index.md +++ b/docs/index.md @@ -8,15 +8,15 @@ id: home
      Keeps the most complex iOS user interfaces smooth and responsive.
      Get Started - View on GitHub + View on GitHub
      -

      AsyncDisplayKit is an iOS framework built on top of UIKit that keeps even the most complex user interfaces smooth and responsive. It was originally built to make Facebook's Paper possible, and goes hand-in-hand with pop's physics-based animations — but it's just as powerful with UIKit Dynamics and conventional app designs. More recently, it was used to power Pinterest's app rewrite.

      +

      Texture is an iOS framework built on top of UIKit that keeps even the most complex user interfaces smooth and responsive. It was originally built to make Facebook's Paper possible, and goes hand-in-hand with pop's physics-based animations — but it's just as powerful with UIKit Dynamics and conventional app designs. More recently, it was used to power Pinterest's app rewrite.

      -

      As the framework has grown, many features have been added that can save developers tons of time by eliminating common boilerplate style structures common in modern iOS apps. If you've ever dealt with cell reuse bugs, tried to performantly preload data for a page or scroll style interface or even just tried to keep your app from dropping too many frames you can benefit from integrating ASDK.

      +

      As the framework has grown, many features have been added that can save developers tons of time by eliminating common boilerplate style structures common in modern iOS apps. If you've ever dealt with cell reuse bugs, tried to performantly preload data for a page or scroll style interface or even just tried to keep your app from dropping too many frames you can benefit from integrating Texture.

      To learn more, check out our docs!

      diff --git a/docs/showcase.md b/docs/showcase.md index 21b361cf7..ab6c06123 100755 --- a/docs/showcase.md +++ b/docs/showcase.md @@ -7,8 +7,8 @@ permalink: /showcase.html
      -

      Who's using AsyncDisplayKit?

      -

      If you're curious to see what can be accomplished with AsyncDisplayKit, check out these apps.

      +

      Who's using Texture?

      +

      If you're curious to see what can be accomplished with Texture, check out these apps.

      @@ -192,8 +192,8 @@ permalink: /showcase.html

      -

      If you built an app using AsyncDisplayKit, we'd love to have your app in this showcase!

      -

      If you would like to have your app added or do not want your app featured on this page, please email asyncdisplaykit@gmail.com.

      +

      If you built an app using Texture, we'd love to have your app in this showcase!

      +

      If you would like to have your app added or do not want your app featured on this page, please email textureframework@gmail.com.

      diff --git a/docs/slack.md b/docs/slack.md index 6bb7f2e03..121dc4d51 100755 --- a/docs/slack.md +++ b/docs/slack.md @@ -7,4 +7,4 @@ permalink: /slack.html -If the auto-invite link above does not work for you, please email asyncdisplaykit@gmail.com for an invite. +If the auto-invite link above does not work for you, please email textureframework@gmail.com for an invite.