Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html/extensions/Variables/includes/ExtVariables.php on line 198
PSDetailController: Difference between revisions - iPhone Development Wiki

PSDetailController: Difference between revisions

From iPhone Development Wiki
m (Added back the header link.)
m (Unnecessary change inconsistent with standard)
 
Line 1: Line 1:
[[PSDetailController]] is a view controller controlling a custom [[PSEditingPane|editing pane]].  
[[PSDetailController]] is a view controller controlling a custom [[PSEditingPane|editing pane]].  


= Detail controller in Specifier plist =
== Detail controller in Specifier plist ==


PSDetailController is in fact a misnomer, because the ''detail'' key in the [[preferences specifier plist]] can be any [[PSViewController]] (usually a subclass of [[PSListController]]). Actually, the only requirement of the ''detail'' key is the class must adopt the informal protocol
PSDetailController is in fact a misnomer, because the ''detail'' key in the [[preferences specifier plist]] can be any [[PSViewController]] (usually a subclass of [[PSListController]]). Actually, the only requirement of the ''detail'' key is the class must adopt the informal protocol
Line 42: Line 42:
</source>
</source>


= External links =
== External links ==


* Header: http://github.com/kennytm/iphone-private-frameworks/blob/master/Preferences/PSDetailController.h
* Header: http://github.com/kennytm/iphone-private-frameworks/blob/master/Preferences/PSDetailController.h

Latest revision as of 02:58, 11 April 2016

PSDetailController is a view controller controlling a custom editing pane.

Detail controller in Specifier plist

PSDetailController is in fact a misnomer, because the detail key in the preferences specifier plist can be any PSViewController (usually a subclass of PSListController). Actually, the only requirement of the detail key is the class must adopt the informal protocol

@protocol PSDetailController <PSViewController>
-(id)initForContentSize:(CGSize)size;
-(void)viewWillBecomeVisible:(PSSpecifier*)spec;
-(void)handleURL:(NSURL*)url;
@optional
+(void)validateSpecifier:(PSSpecifier*)srcSpecifier;
@end

The detail controller class will be sent a +validateSpecifier: message if one exists right after the bundle is lazy-loaded:

@implementation PSRootController
...
-(void)lazyLoadBundle:(PSSpecifier*)srcSpecifier {
        ...
        if ([srcSpecifier->detailControllerClass respondsToSelector:@selector(validateSpecifier:)])
                [srcSpecifier->detailControllerClass validateSpecifier:srcSpecifier];
}
...
@end

Whenever a view becomes visible, a detail controller class instance will be allocated with -initForContentSize:, and then call -viewWillBecomeVisible: to notify that the view becomes visibile. There is also some other calls to the controller but you'd better leave them untouched.

...
id<PSDetailController> detailController = [[[spec->detailControllerClass alloc]
                                                                         initForContentSize:someListController.view.bounds.size]
                                                                         autorelease];
detailController.rootController = _parentController.rootController;
detailController.parentController = _parentController;
[detailController viewWillBecomeVisible:spec];
...

External links