vamsiac

import CoreGraphics
import SpriteKit

extension SKAction {

    static func transitionStrokeColor(from: SKColor, to: SKColor, duration: TimeInterval) -> SKAction {
        return transitionColor(from: from, to: to, duration: duration, fill: false)
    }

    static func transitionFillColor(from: SKColor, to: SKColor, duration: TimeInterval) -> SKAction {

vamsiac

import UIKit
import CoreData

class FRCTableViewDataSource: NSObject, UITableViewDataSource {
    private unowned let fetchedResultsController: NSFetchedResultsController<NSFetchRequestResult>
    let configureCell: (UITableViewCell, IndexPath)-> ()

    init(fetchController: NSFetchedResultsController<NSFetchRequestResult>, configureBlock: @escaping (UITableViewCell, IndexPath)-> ()) {
        self.fetchedResultsController = fetchController
        self.configureCell = configureBlock

vamsiac

import UIKit
import CoreData

public class FRCDelegate: NSObject, NSFetchedResultsControllerDelegate {
    
    private unowned let tableView: UITableView
    
    init(tableView: UITableView) {
        self.tableView = tableView
        super.init()

vamsiac

import UIKit

typealias DownloadCompletionBlock = (UIImage?) -> Void

class AsyncImageView: UIImageView {
    
    /// Returns the cached image or nil if connection fails.
    var completionHandler:((UIImage?)->Void)?
    
    /// Sets the cache policy for the image download request. Default values is .returnCacheDataElseLoad.

vamsiac

import UIKit

protocol CustomAccessoryToolbarDelegate {
    var userEnabledFields: [UIView]! {get set}
    func previousButtonClicked(_ sender: UIView)
    func nextButtonClicked(_ sender: UIView)
    func doneButtonClicked(_ sender: UIView)
}

extension CustomAccessoryToolbarDelegate where Self: UIViewController {

vamsiac

Asynchronous Error Handling in Swift 2.0

As Swift 1.0 did not include support for exceptions, a common error handling pattern was to use a Result enum that either took on a value on success, or an error on failure. In a way, this was superior to using exceptions, since being a instantiable type, Results could be passed around freely, enabling asynchronous code to use the same error handling mechanisim as synchronous code. Using Swift's robust support for custom operators, this also enabled Railway Oriented Programming for more functional oriented programers.

Swift 2.0 introduces throwable errors, which are similar to exceptions. However, like exceptions, thrown errors

vamsiac

import CoreData

protocol Fetchable
{
    associatedtype FetchableType: NSManagedObject = Self
    
    static func entityName() -> String
    static func objectsInContext(_ context: NSManagedObjectContext, predicate: NSPredicate?, sortedBy: String?, ascending: Bool) throws -> [FetchableType]
    static func singleObjectInContext(_ context: NSManagedObjectContext, predicate: NSPredicate?, sortedBy: String?, ascending: Bool) throws -> FetchableType?
    static func objectCountInContext(_ context: NSManagedObjectContext, predicate: NSPredicate?) -> Int

vamsiac

// Swift Standard Librray - String
// Keith Harrison http://useyourloaf.com

// Import Foundation if you want to bridge to NSString
import Foundation

// ====
// Initializing a String
// ====

vamsiac

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

vamsiac

//Appdelegate.h
CFAbsoluteTime StartTime;  
@interface AppDelegate : UIResponder <UIApplicationDelegate>

@end

//In your main.m start your timer
int main(int argc, char *argv[])
{
    StartTime = CFAbsoluteTimeGetCurrent();