kylefang/AsyncDisplayKit
1
0
Fork 0
mirror of https://github.com/HackPlan/AsyncDisplayKit.git synced 2026-04-01 22:36:03 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
f748cf728af008d94de6152505f79246da2e314c
AsyncDisplayKit/_docs/containers-overview.md
Hannah Troisi 8a410f675c Update containers-overview.md
2016-07-17 20:29:10 -07:00

1.4 KiB
Raw Blame History

title, layout, permalink, prevPage, nextPage
title layout permalink prevPage nextPage
Node Containers docs /docs/containers-overview.html intelligent-preloading.html subclassing.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

  • ASViewController in place of UIKit's UIViewController
  • ASCollectionNode in place of UIKit's UICollectionView
  • ASPagerNode in place of UIKit's UIPageViewController
  • ASTableNode in place of UIKit's UITableView

Example code and specific sample projects are highlighted in the documentation for each node container.

For a detailed description on porting an existing UIKit app to AsyncDisplayKit, read the porting guide.

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 reccomended 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.