| // request Game Center verification data for localPlayer from apple | |
| - (void)authenticateGameCenterPlayer:(GKLocalPlayer *)localPlayer | |
| { | |
| [localPlayer generateIdentityVerificationSignatureWithCompletionHandler:^(NSURL *publicKeyUrl, NSData *signature, NSData *salt, uint64_t timestamp, NSError *error) { | |
| if (error) { | |
| NSLog(@"ERROR: %@", error); | |
| } | |
| else { | |
| // package data to be sent to server for verification | |
| NSDictionary *params = @{@"publicKeyUrl": publicKeyUrl, |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| #!/usr/bin/env python | |
| # coding: utf-8 | |
| # How Twisted's inlineCallbacks work? | |
| # If you use it but don't know exactly what it does, | |
| # and didn't understand the code shipped with Twisted, | |
| # keep reading. | |
| import types, functools | |
| from twisted.python import failure | |
| from twisted.web.client import getPage |
