03592e0669
This was originally added for ASCollectionNode and ASTableNode preloading to work as intended when nested inside of another ASRangeController-powered node. Indeed, it is still necessary to trigger layout on these UIKit-backed components in order for their own ASRangeControllers to start preparing content within them. However, unlike the comment suggests, it is *not* necessary to do this for image nodes. ASNetworkImageNode has only one .URL, and does not use the .bounds or .calculatedLayout at all during loading. Even the ASMultiplexImageNode does not use the .bounds, and the ASMapNode uses .calculatedLayout instead of .bounds. This change has important performance benefits. In particular, it avoids layouts that would occur on the main thread, often including text sizing, and also can result in redundant layout passes (even during a layout pass that triggers a node to enter the preload range, it may force its own layout early). It would be great to test this change with Pinterest to confirm its safety, but based on a full audit of the framework codebase, the only possibility that I see for a regression is if app implementations of -didEnterPreloadState make direct use of .bounds instead of .calculatedLayout (which is easy to fix).
Coming from AsyncDisplayKit? Learn more here
Installation
Texture is available via CocoaPods or Carthage. See our Installation guide for instructions.
Performance Gains
Texture's basic unit is the node. An 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 threads.
To keep its user interface smooth and responsive, your app should render at 60 frames per second — the gold standard on iOS. This means the main thread 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.
Texture lets you move image decoding, text sizing and rendering, layout, and other expensive UI operations off the main thread, to keep the main thread available to respond to user interaction.
Advanced Developer Features
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.
Learn More
- Read the our Getting Started guide
- Get the sample projects
- Browse the API reference
Getting Help
We use Slack for real-time debugging, community updates, and general talk about Texture. Signup yourself or email textureframework@gmail.com to get an invite.
Contributing
We welcome any contributions. See the CONTRIBUTING file for how to get involved.
License
The Texture project was created by Pinterest as a continuation, under a different name and license, of the AsyncDisplayKit codebase originally developed by Facebook. AsyncDisplayKit was originally released by Facebook under a BSD license and additional patent grant. Those BSD and patent licenses govern use of code in Texture contributed prior to 4/13/2017 (the original AsyncDisplayKit code), and copies of the licenses are included in the root directory of this source tree for reference. All code contributed to Texture after 4/13/2017 is released by Pinterest under an Apache 2.0 license.