#IFLKit# IFLKit is a Interfacelift.com wrapper, written in Objective-C.

#Getting Started#

IFLKit requires a private key provided by Interfacelift.com. To obtain a private key you will need to register for an account at Interfacelift.com and request a private key at api.ifl.cc.

IFLKit is structured around the IFLClient class. The IFLClient class manages both authentication and communication with the provider. To create an instance of IFLClient call the initWithPrivateKey initalizer.

// Create instance
IFLClient* client = [[IFLClient alloc]initWithPrivateKey:@"YOUR-PRIVATE-KEY"];

IFLClient is not a singleton class, but does provide a class level instance that can be shared throughout your application.

// Register instance
[client registerAsSharedClient];

Once you have registered your shared client you can easily access your shared instance by calling the IFLClient sharedClient method.

// Access shared Instance
[IFLClient sharedClient];

All request are descendents of the IFLRequest class. The following example will download the ten most recent wallpaper submissions since the provided unix timestamp.

NSNumber* unixTimestamp = @1396378800;
NSNumber* limit = @10;

IFLWallpaperByTimestampRequest *req =
 [[IFLWallpaperByTimestampRequest alloc]initWithTimestamp:unixTimestamp];
 req.limit = limit;

 [req setSuccessBlock:^(id data, NSHTTPURLResponse* resp, NSError* error){
  // Handle success
 }];

 [req setFailureBlock:^(id data, NSHTTPURLResponse* resp, NSError* error){
  // Handle Failure
 }];

[[IFLClient sharedClient]processRequest:req];

Note Users that are not using a shared client, but instead have a strong reference to a locally created instance, should pay special attention to avoiding retain cycles. All IFLRequest are subclasses of NSOperation and are managed by a local NSOperationQueue in the IFLClient. If you need to make references to self in these instances you should create a weak reference first and refer to that reference.

Both the success & failure block are passed back the payload of the HTTP request. Both are passed back and NSData payload containing the content of the request.

Both the success and failure blocks are called on a background thread. Any UI updates that need to take place should be added to the main queue. You can easily do this by adding a block to the main operation queue.

[[NSOperationQueue mainQueue]addOperationWithBlock^{
 // Update view state
}];