floriankugler

NSURLConnection                                                                                             | NSURLSession
------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------
NSURLConnectionDelegate            connectionShouldUseCredentialStorage:                                    |
------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------
NSURLConnectionDelegate            connection:willSendRequestForAuthenticationChallenge:                    | NSURLSessionDelegate            URLSession:didReceiveChallenge:completionHandler:
                                                                                                            | N

couchdeveloper

//
//  SimpleGetHTTPRequest.h
//

#import <Foundation/Foundation.h>


typedef void (^completionHandler_t) (id result);

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

jeremy-w

//clang++ -std=c++11 -stdlib=libc++ -framework Foundation nsarray.mm -o nsarray
/* Note:
 * - libstdc++ has been frozen by Apple at a pre-C++11 version, so you must opt
     for the newer, BSD-licensed libc++
 * - Apple clang 4.0 (based on LLVM 3.1svn) does not default to C++11 yet, so
     you must explicitly specify this language standard. */
/* @file nsarray.mm
 * @author Jeremy W. Sherman
 *
 * Demonstrates three different approaches to converting a std::vector

iros

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

• URL

  <The URL Structure (path only, no root url)>

• Method:

sekati

# xcode-build-bump.sh
# @desc Auto-increment the build number every time the project is run. 
# @usage
# 1. Select: your Target in Xcode
# 2. Select: Build Phases Tab
# 3. Select: Add Build Phase -> Add Run Script
# 4. Paste code below in to new "Run Script" section
# 5. Drag the "Run Script" below "Link Binaries With Libraries"
# 6. Insure that your starting build number is set to a whole integer and not a float (e.g. 1, not 1.0)

tomohisa

// add child view
    UIViewController* controller = [self.storyboard instantiateViewControllerWithIdentifier:@"test"];
    [self addChildViewController:controller];
    controller.view.frame = CGRectMake(0, 44, 320, 320);
    [self.view addSubview:controller.view];
    [controller didMoveToParentViewController:self];

// remove child view
    UIViewController *vc = [self.childViewControllers lastObject];
    [vc.view removeFromSuperview];

steipete

This was nice and fast... but it takes up WAY TOO MUCH space. And it's annoying to write.
(I like the way I can just step into the function that calls the delegate for debugging)

What's a better way to not make me call respondsToSelector in the middle of my code? Some proxy?

    struct {
        unsigned int delegateWillDisplayDocument:1;
        unsigned int delegateDidDisplayDocument:1;
        unsigned int delegateDidShowPageView:1;
        unsigned int delegateDidRenderPageView:1;