From e88783e920f2f279e9f234457848e08171e2f76b Mon Sep 17 00:00:00 2001 From: Joe Ferrucci <2114494+JoeFerrucci@users.noreply.github.com> Date: Wed, 5 Apr 2023 13:30:08 -0500 Subject: [PATCH] Docs: Fix references of ASViewController/ASNavigationController (non-existent) to ASDKViewController/ASDKNavigationController (#2072) * Fix references of ASViewController (non-existent) to ASDKViewController * More references changes to old ASViewController * Also update ASNavigationController -> ASDKNavigationController --- docs/_data/nav_docs.yml | 2 +- docs/_docs/asrunloopqueue.md | 2 +- docs/_docs/asvisibility.md | 6 +- docs/_docs/button-node.md | 2 +- docs/_docs/cell-node.md | 4 +- docs/_docs/containers-ascollectionnode.md | 8 +-- docs/_docs/containers-asdkviewcontroller.md | 67 +++++++++++++++++++ docs/_docs/containers-asnodecontroller.md | 2 +- docs/_docs/containers-aspagernode.md | 16 ++--- docs/_docs/containers-astablenode.md | 8 +-- docs/_docs/containers-asviewcontroller.md | 67 ------------------- docs/_docs/containers-overview.md | 4 +- docs/_docs/development/overview.md | 2 +- docs/_docs/layout-options.md | 2 +- ...ASRangeControllerUpdateRangeProtocol.html} | 8 +-- ...ler.html => ASDKNavigationController.html} | 10 +-- ...ontroller.html => ASDKViewController.html} | 24 +++---- docs/appledoc/Constants/ASInterfaceState.html | 2 +- .../ASManagesChildVisibilityDepth.html | 2 +- .../appledoc/Protocols/ASVisibilityDepth.html | 8 +-- docs/appledoc/hierarchy.html | 6 +- docs/appledoc/index.html | 6 +- 22 files changed, 129 insertions(+), 129 deletions(-) create mode 100755 docs/_docs/containers-asdkviewcontroller.md delete mode 100755 docs/_docs/containers-asviewcontroller.md rename docs/appledoc/Categories/{ASViewController+ASRangeControllerUpdateRangeProtocol.html => ASDKViewController+ASRangeControllerUpdateRangeProtocol.html} (92%) rename docs/appledoc/Classes/{ASNavigationController.html => ASDKNavigationController.html} (86%) rename docs/appledoc/Classes/{ASViewController.html => ASDKViewController.html} (92%) diff --git a/docs/_data/nav_docs.yml b/docs/_data/nav_docs.yml index 3a06100ae..3c3b14fc8 100755 --- a/docs/_data/nav_docs.yml +++ b/docs/_data/nav_docs.yml @@ -46,7 +46,7 @@ - asrunloopqueue - title: Node Containers items: - - containers-asviewcontroller + - containers-asdkviewcontroller - containers-asnodecontroller - containers-astablenode - containers-ascollectionnode diff --git a/docs/_docs/asrunloopqueue.md b/docs/_docs/asrunloopqueue.md index ea55c1eb7..69df27a10 100755 --- a/docs/_docs/asrunloopqueue.md +++ b/docs/_docs/asrunloopqueue.md @@ -3,7 +3,7 @@ title: ASRunLoopQueue layout: docs permalink: /docs/asrunloopqueue.html prevPage: asvisibility.html -nextPage: containers-asviewcontroller.html +nextPage: containers-asdkviewcontroller.html --- Even with main thread work, Texture is able to dramatically reduce its impact on the user experience by way of the rather amazing ASRunLoopQueue. diff --git a/docs/_docs/asvisibility.md b/docs/_docs/asvisibility.md index f021d013a..a9b7f7fed 100755 --- a/docs/_docs/asvisibility.md +++ b/docs/_docs/asvisibility.md @@ -6,10 +6,10 @@ prevPage: debug-tool-ASRangeController.html nextPage: asrunloopqueue.html --- -`ASNavigationController` and `ASTabBarController` both implement the `ASVisibility` protocol. These classes can be used even without `ASDisplayNodes`, making them suitable base classes for your inheritance hierarchy. For any child view controllers that are `ASViewControllers`, these classes know the exact number of user taps it would take to make the view controller visible (0 if currently visible). +`ASDKNavigationController` and `ASTabBarController` both implement the `ASVisibility` protocol. These classes can be used even without `ASDisplayNodes`, making them suitable base classes for your inheritance hierarchy. For any child view controllers that are `ASDKViewControllers`, these classes know the exact number of user taps it would take to make the view controller visible (0 if currently visible). Knowing a view controller’s visibility depth allows view controllers to automatically take appropriate actions as a user approaches or leaves them. Non-default tabs in an app might preload some of their data; a controller 3 levels deep in a navigation stack might progressively free memory for images, text, and fetched data as it gets deeper. -Any container view controller can implement a simple protocol to integrate with the system. For example, `ASNavigationController` will return a visibility depth of it's own `visibilityDepth` + 1 for a view controller that would be revealed by tapping the back button once. +Any container view controller can implement a simple protocol to integrate with the system. For example, `ASDKNavigationController` will return a visibility depth of it's own `visibilityDepth` + 1 for a view controller that would be revealed by tapping the back button once. -You can opt into some of this behavior automatically by enabling `automaticallyAdjustRangeModeBasedOnViewEvents` on `ASViewController`s. With this enabled, if either the view controller or its node conform to `ASRangeControllerUpdateRangeProtocol` (`ASCollectionNode` and `ASTableNode` do by default), the ranges will automatically be decreased as the visibility depth increases to save memory. +You can opt into some of this behavior automatically by enabling `automaticallyAdjustRangeModeBasedOnViewEvents` on `ASDKViewController`s. With this enabled, if either the view controller or its node conform to `ASRangeControllerUpdateRangeProtocol` (`ASCollectionNode` and `ASTableNode` do by default), the ranges will automatically be decreased as the visibility depth increases to save memory. diff --git a/docs/_docs/button-node.md b/docs/_docs/button-node.md index 11eb6ca95..16e96805e 100755 --- a/docs/_docs/button-node.md +++ b/docs/_docs/button-node.md @@ -90,7 +90,7 @@ Let's say you want to add an `ASButtonNode` to the view of one of your existing The next thing you'll notice is that, if you set titles of various lengths for different control states, the button will dynamically grow and shrink as the title changes. This is because changing the title causes `-setNeedsLayout` to be called on the button. Within a node hierarchy, this makes sense, and will work as expected. -Long story short, use an `ASViewController`. +Long story short, use an `ASDKViewController`. ##### Selected State diff --git a/docs/_docs/cell-node.md b/docs/_docs/cell-node.md index 60b1cfad3..03c45f528 100755 --- a/docs/_docs/cell-node.md +++ b/docs/_docs/cell-node.md @@ -10,7 +10,7 @@ nextPage: button-node.html ### 3 Ways to Party -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`. +There are three ways in which you can implement the cells you'll use in your Texture app: subclassing `ASCellNode`, initializing with an existing `ASDKViewController` or using an existing UIView or `CALayer`. #### Subclassing @@ -24,7 +24,7 @@ Most likely, you'll write a few of the following: - `-layout` -- Also called on the main thread. Layout is complete after the call to super which means you can do any extra tweaking you need to do. -#### Initializing with an `ASViewController` +#### Initializing with an `ASDKViewController` Say you already have some type of view controller written to display a view in your app. If you want to take that view controller and drop its view in as a cell in one of the scrolling nodes or a pager node its no problem. diff --git a/docs/_docs/containers-ascollectionnode.md b/docs/_docs/containers-ascollectionnode.md index 780e5c3ad..cae972f87 100755 --- a/docs/_docs/containers-ascollectionnode.md +++ b/docs/_docs/containers-ascollectionnode.md @@ -116,13 +116,13 @@ func collectionNode(_ collectionNode: ASCollectionNode, nodeBlockForItemAt index In the example above, you can see how the index is used to access the photo model before creating the node block. -### Replacing a UICollectionViewController with an ASViewController +### Replacing a UICollectionViewController with an ASDKViewController -Texture 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 ASDKViewController to recreate any type of UI...ViewController. -Consider, the following ASViewController subclass. +Consider, the following ASDKViewController subclass. -An ASCollectionNode is assigned to be managed by an `ASViewController` in its `-initWithNode:` designated initializer method, thus making it a sort of ASCollectionNodeController. +An ASCollectionNode is assigned to be managed by an `ASDKViewController` in its `-initWithNode:` designated initializer method, thus making it a sort of ASCollectionNodeController.
SwiftObjective-C diff --git a/docs/_docs/containers-asdkviewcontroller.md b/docs/_docs/containers-asdkviewcontroller.md new file mode 100755 index 000000000..fcf1755a2 --- /dev/null +++ b/docs/_docs/containers-asdkviewcontroller.md @@ -0,0 +1,67 @@ +--- +title: ASDKViewController +layout: docs +permalink: /docs/containers-asdkviewcontroller.html +prevPage: asrunloopqueue.html +nextPage: containers-asnodecontroller.html +--- + +`ASDKViewController` is a subclass of `UIViewController` that adds several useful features for hosting `ASDisplayNode` hierarchies. + +An `ASDKViewController` can be used in place of any `UIViewController` - including within a `UINavigationController`, `UITabBarController` and `UISplitViewController` or as a modal view controller. + +Benefits of using an `ASDKViewController`: +
    +
  1. Save Memory. An ASDKViewController that goes off screen will automatically reduce the size of the fetch data and display ranges of any of its children. This is key for memory management in large applications.
    2. +
  2. ASVisibility Feature. When used in an ASDKNavigationController or ASTabBarController, these classes know the exact number of user taps it would take to make the view controller visible.
    3. +
+ +More features will be added over time, so it is a good idea to base your view controllers off of this class. + +## Usage + +A `UIViewController` provides a view of its own. An `ASDKViewController` is assigned a node to manage in its designated initializer `-initWithNode:`. + +Consider the following `ASDKViewController` 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 `ASDKViewController` in its `-initWithNode:` designated initializer method. + +
+SwiftObjective-C +
+ 
+- (instancetype)init
+{
+  _tableNode = [[ASTableNode alloc] initWithStyle:UITableViewStylePlain];
+  self = [super initWithNode:_tableNode];
+  
+  if (self) {
+    _tableNode.dataSource = self;
+    _tableNode.delegate = self;
+  }
+  
+  return self;
+}
+
+ + +
+
+ +
+
+Conversion Tip: If your app already has a complex view controller hierarchy, it is perfectly fine to have all of them subclass ASDKViewController. That is to say, even if you don't use ASDKViewController's designated initializer -initWithNode:, and only use the ASDKViewController in the manner of a traditional UIViewController, this will give you the additional node support if you choose to adopt it in different areas your application. +
+ diff --git a/docs/_docs/containers-asnodecontroller.md b/docs/_docs/containers-asnodecontroller.md index 09b644440..928ff730d 100755 --- a/docs/_docs/containers-asnodecontroller.md +++ b/docs/_docs/containers-asnodecontroller.md @@ -2,7 +2,7 @@ title: "ASNodeController (Beta)" layout: docs permalink: /docs/containers-asnodecontroller.html -prevPage: containers-asviewcontroller.html +prevPage: containers-asdkviewcontroller.html nextPage: containers-astablenode.html --- diff --git a/docs/_docs/containers-aspagernode.md b/docs/_docs/containers-aspagernode.md index f538983ee..2d50c7632 100755 --- a/docs/_docs/containers-aspagernode.md +++ b/docs/_docs/containers-aspagernode.md @@ -100,9 +100,9 @@ func pagerNode(_ pagerNode: ASPagerNode, nodeBlockAt index: Int) -> ASCellNodeBl
-### Using an ASViewController For Optimal Performance +### Using an ASDKViewController For Optimal Performance -One especially useful pattern is to return an `ASCellNode` that is initialized with an existing `UIViewController` or `ASViewController`. For optimal performance, use an `ASViewController`. +One especially useful pattern is to return an `ASCellNode` that is initialized with an existing `UIViewController` or `ASDKViewController`. For optimal performance, use an `ASDKViewController`.
SwiftObjective-C @@ -141,21 +141,21 @@ func pagerNode(_ pagerNode: ASPagerNode, nodeAt index: Int) -> ASCellNode { In this example, you can see that the node is constructed using the `-initWithViewControllerBlock:` method. It is usually necessary to provide a cell created this way with a `style.preferredSize` so that it can be laid out correctly. -### Use ASPagerNode as root node of an ASViewController +### Use ASPagerNode as root node of an ASDKViewController #### Log message while popping back in the view controller hierarchy -If you use an `ASPagerNode` embedded in an `ASViewController` in full screen. If you pop back from the view controller hierarchy you will see some error message in the console. +If you use an `ASPagerNode` embedded in an `ASDKViewController` in full screen. If you pop back from the view controller hierarchy you will see some error message in the console. -To resolve the error message set `self.automaticallyAdjustsScrollViewInsets = NO;` in `viewDidLoad` in your `ASViewController` subclass. +To resolve the error message set `self.automaticallyAdjustsScrollViewInsets = NO;` in `viewDidLoad` in your `ASDKViewController` subclass. #### `navigationBar.translucent` is set to YES -If you have an `ASPagerNode` embedded in an `ASViewController` in full screen and set the `navigationBar.translucent` to `YES`, you will see an error message while pushing the view controller on the view controller stack. +If you have an `ASPagerNode` embedded in an `ASDKViewController` in full screen and set the `navigationBar.translucent` to `YES`, you will see an error message while pushing the view controller on the view controller stack. -To resolve the error message add `[self.pagerNode waitUntilAllUpdatesAreCommitted];` within `- (void)viewWillAppear:(BOOL)animated` in your `ASViewController` subclass. +To resolve the error message add `[self.pagerNode waitUntilAllUpdatesAreCommitted];` within `- (void)viewWillAppear:(BOOL)animated` in your `ASDKViewController` subclass. 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 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. +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 `ASDKViewController` 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 diff --git a/docs/_docs/containers-astablenode.md b/docs/_docs/containers-astablenode.md index 7742e23c3..ada601f41 100755 --- a/docs/_docs/containers-astablenode.md +++ b/docs/_docs/containers-astablenode.md @@ -74,13 +74,13 @@ These two methods, need to return either an `ASCellNo Note that neither of these methods require a reuse mechanism. -### Replacing UITableViewController with ASViewController +### Replacing UITableViewController with ASDKViewController -Texture 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 `ASDKViewController` 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 `ASDKViewController` 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. +An `ASTableNode` is assigned to be managed by an `ASDKViewController` in its `-initWithNode:` designated initializer method.
SwiftObjective-C diff --git a/docs/_docs/containers-asviewcontroller.md b/docs/_docs/containers-asviewcontroller.md deleted file mode 100755 index ebd7e0401..000000000 --- a/docs/_docs/containers-asviewcontroller.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: ASViewController -layout: docs -permalink: /docs/containers-asviewcontroller.html -prevPage: asrunloopqueue.html -nextPage: containers-asnodecontroller.html ---- - -`ASViewController` is a subclass of `UIViewController` that adds several useful features for hosting `ASDisplayNode` hierarchies. - -An `ASViewController` can be used in place of any `UIViewController` - including within a `UINavigationController`, `UITabBarController` and `UISplitViewController` or as a modal view controller. - -Benefits of using an `ASViewController`: -
    -
  1. Save Memory. An ASViewController that goes off screen will automatically reduce the size of the fetch data and display ranges of any of its children. This is key for memory management in large applications.
    2. -
  2. ASVisibility Feature. When used in an ASNavigationController or ASTabBarController, these classes know the exact number of user taps it would take to make the view controller visible.
    3. -
- -More features will be added over time, so it is a good idea to base your view controllers off of this class. - -## Usage - -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. - -This table node is assigned to the `ASViewController` in its `-initWithNode:` designated initializer method. - -
-SwiftObjective-C -
- 
-- (instancetype)init
-{
-  _tableNode = [[ASTableNode alloc] initWithStyle:UITableViewStylePlain];
-  self = [super initWithNode:_tableNode];
-  
-  if (self) {
-    _tableNode.dataSource = self;
-    _tableNode.delegate = self;
-  }
-  
-  return self;
-}
-
- - -
-
- -
-
-Conversion Tip: If your app already has a complex view controller hierarchy, it is perfectly fine to have all of them subclass ASViewController. That is to say, even if you don't use ASViewController's designated initializer -initWithNode:, and only use the ASViewController in the manner of a traditional UIViewController, this will give you the additional node support if you choose to adopt it in different areas your application. -
- diff --git a/docs/_docs/containers-overview.md b/docs/_docs/containers-overview.md index cde2fb7f8..dc5a4dfb7 100755 --- a/docs/_docs/containers-overview.md +++ b/docs/_docs/containers-overview.md @@ -27,11 +27,11 @@ It is highly recommended that you use Texture's nodes within a node container. T in place of UIKit's UITableView - ASViewController + ASDKViewController in place of UIKit's UIViewController - ASNavigationController + ASDKNavigationController in place of UIKit's UINavigationController. Implements the ASVisibility protocol. diff --git a/docs/_docs/development/overview.md b/docs/_docs/development/overview.md index 4c659c05c..0dc7439ab 100644 --- a/docs/_docs/development/overview.md +++ b/docs/_docs/development/overview.md @@ -25,7 +25,7 @@ Here are the main directories within the repository: - [Private](https://github.com/TextureGroup/Texture/tree/master/Source/Private): Framework-private files that are not exposed to end users, including implementation details, private data structures and helpers. - [TextKit](https://github.com/TextureGroup/Texture/tree/master/Source/TextKit): All files related to TextKit that are used by ASTextNode. - [tvOS](https://github.com/TextureGroup/Texture/tree/master/Source/tvOS): tvOS support. - - All other files in the [Source](https://github.com/TextureGroup/Texture/tree/master/Source) directory: Main files, including important components such as nodes (e.g ASDisplayNode, ASButtonNode, ASImageNode, ASCollectionNode and ASTableNode), ASNavigationController, etc. + - All other files in the [Source](https://github.com/TextureGroup/Texture/tree/master/Source) directory: Main files, including important components such as nodes (e.g ASDisplayNode, ASButtonNode, ASImageNode, ASCollectionNode and ASTableNode), ASDKNavigationController, etc. - [Tests](https://github.com/TextureGroup/Texture/tree/master/Tests): The framework's test suite, including unit, integration and snapshot test cases. - [docs](https://github.com/TextureGroup/Texture/tree/master/docs): Texture documentation that powers [texturegroup.org](https://texturegroup.org/). - [examples](https://github.com/TextureGroup/Texture/tree/master/examples): Sample projects which demonstrate how to use various features of the framework. diff --git a/docs/_docs/layout-options.md b/docs/_docs/layout-options.md index 709a7f8be..46b368923 100755 --- a/docs/_docs/layout-options.md +++ b/docs/_docs/layout-options.md @@ -9,7 +9,7 @@ nextPage: layer-backing.html 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 Texture 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 ASDKViewControllers (unless you subclass the node). `[ASDisplayNode calculateSizeThatFits:]` **vs.** `[UIView sizeThatFits:]` diff --git a/docs/appledoc/Categories/ASViewController+ASRangeControllerUpdateRangeProtocol.html b/docs/appledoc/Categories/ASDKViewController+ASRangeControllerUpdateRangeProtocol.html similarity index 92% rename from docs/appledoc/Categories/ASViewController+ASRangeControllerUpdateRangeProtocol.html rename to docs/appledoc/Categories/ASDKViewController+ASRangeControllerUpdateRangeProtocol.html index 0c0d6ab95..7c055d815 100755 --- a/docs/appledoc/Categories/ASViewController+ASRangeControllerUpdateRangeProtocol.html +++ b/docs/appledoc/Categories/ASDKViewController+ASRangeControllerUpdateRangeProtocol.html @@ -3,7 +3,7 @@ - ASViewController(ASRangeControllerUpdateRangeProtocol) Category Reference + ASDKViewController(ASRangeControllerUpdateRangeProtocol) Category Reference @@ -75,13 +75,13 @@

-

ASViewController(ASRangeControllerUpdateRangeProtocol) Category Reference

+

ASDKViewController(ASRangeControllerUpdateRangeProtocol) Category Reference

- +
Declared inASViewController.hASDKViewController.h
@@ -139,7 +139,7 @@

Discussion

Declared In

-

ASViewController.h

+

ASDKViewController.h

diff --git a/docs/appledoc/Classes/ASNavigationController.html b/docs/appledoc/Classes/ASDKNavigationController.html similarity index 86% rename from docs/appledoc/Classes/ASNavigationController.html rename to docs/appledoc/Classes/ASDKNavigationController.html index 4dd2da497..650a2ae50 100755 --- a/docs/appledoc/Classes/ASNavigationController.html +++ b/docs/appledoc/Classes/ASDKNavigationController.html @@ -3,7 +3,7 @@ - ASNavigationController Class Reference + ASDKNavigationController Class Reference @@ -69,7 +69,7 @@

-

ASNavigationController Class Reference

+

ASDKNavigationController Class Reference

@@ -81,7 +81,7 @@

ASNavigationController Class Reference

- +
ASManagesChildVisibilityDepth
Declared inASNavigationController.hASDKNavigationController.h
@@ -91,9 +91,9 @@

ASNavigationController Class Reference

Overview

-

ASNavigationController

ASNavigationController is a drop in replacement for UINavigationController +

ASDKNavigationController

ASDKNavigationController is a drop in replacement for UINavigationController which improves memory efficiency by implementing the @c ASManagesChildVisibilityDepth protocol. -You can use ASNavigationController with regular UIViewControllers, as well as ASViewControllers. +You can use ASDKNavigationController with regular UIViewControllers, as well as ASDKViewControllers. It is safe to subclass or use even where AsyncDisplayKit is not adopted.

diff --git a/docs/appledoc/Classes/ASViewController.html b/docs/appledoc/Classes/ASDKViewController.html similarity index 92% rename from docs/appledoc/Classes/ASViewController.html rename to docs/appledoc/Classes/ASDKViewController.html index d29e08e03..4b05809e0 100755 --- a/docs/appledoc/Classes/ASViewController.html +++ b/docs/appledoc/Classes/ASDKViewController.html @@ -3,7 +3,7 @@ - ASViewController Class Reference + ASDKViewController Class Reference @@ -89,7 +89,7 @@

@@ -365,7 +365,7 @@

See Also

Declared In

-

ASViewController.h

+

ASDKViewController.h

@@ -413,7 +413,7 @@

Discussion

Declared In

-

ASViewController.h

+

ASDKViewController.h

diff --git a/docs/appledoc/Constants/ASInterfaceState.html b/docs/appledoc/Constants/ASInterfaceState.html index ab0706f83..4182ee0a9 100755 --- a/docs/appledoc/Constants/ASInterfaceState.html +++ b/docs/appledoc/Constants/ASInterfaceState.html @@ -79,7 +79,7 @@

ASInterfaceState

-

Interface state is available on ASDisplayNode and ASViewController, and +

Interface state is available on ASDisplayNode and ASDKViewController, and allows checking whether a node is in an interface situation where it is prudent to trigger certain actions: measurement, data loading, display, and visibility (the latter for animations or other onscreen-only effects).

diff --git a/docs/appledoc/Protocols/ASManagesChildVisibilityDepth.html b/docs/appledoc/Protocols/ASManagesChildVisibilityDepth.html index 817097a2b..8748e6cd5 100755 --- a/docs/appledoc/Protocols/ASManagesChildVisibilityDepth.html +++ b/docs/appledoc/Protocols/ASManagesChildVisibilityDepth.html @@ -125,7 +125,7 @@

Container view controllers should adopt this protocol to indicate that they will manage their child’s -visibilityDepth. For example, ASNavigationController adopts this protocol and manages its childrens visibility +visibilityDepth. For example, ASDKNavigationController adopts this protocol and manages its childrens visibility depth.

If you adopt this protocol, you must also emit visibilityDepthDidChange messages to child view controllers.

diff --git a/docs/appledoc/Protocols/ASVisibilityDepth.html b/docs/appledoc/Protocols/ASVisibilityDepth.html index 29597c887..4e6267ff8 100755 --- a/docs/appledoc/Protocols/ASVisibilityDepth.html +++ b/docs/appledoc/Protocols/ASVisibilityDepth.html @@ -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. Texture uses this information to intelligently manage memory and focus +ASDKViewController 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.

@@ -205,13 +205,13 @@

Discussion

has changed.

If implemented by a view controller container, use this method to notify child view controllers that their view -depth has changed @see ASNavigationController.m

+depth has changed @see ASDKNavigationController.m

-

If implemented on an ASViewController, use this method to reduce or increase the resources that your +

If implemented on an ASDKViewController, use this method to reduce or increase the resources that your view controller uses. A higher visibility depth view controller should decrease it’s resource usage, a lower visibility depth controller should pre-warm resources in preperation for a display at 0 depth.

-

ASViewController implements this method and reduces / increases range mode of supporting nodes (such as ASCollectionNode +

ASDKViewController implements this method and reduces / increases range mode of supporting nodes (such as ASCollectionNode and ASTableNode).

diff --git a/docs/appledoc/hierarchy.html b/docs/appledoc/hierarchy.html index f9eb61138..3830fe769 100755 --- a/docs/appledoc/hierarchy.html +++ b/docs/appledoc/hierarchy.html @@ -112,7 +112,7 @@

Class Hierarchy

-
  • ASViewController
    • +
  • ASDKViewController
  • NSObject