joshaber

self.startButton.rac_command = [RACCommand command];
self.stopButton.rac_command = [RACCommand command];

__unsafe_unretained id weakSelf = self;
id<RACSignal> tick = [[[[self.startButton.rac_command
    map:^(id _) {
        RTAFirstView *strongSelf = weakSelf;
        // Map each start button click to a new signal that fires every second
        // and stops when the stop button is clicked.
        return [[RACSignal interval:1] takeUntil:strongSelf.stopButton.rac_command];

austinzheng

import Foundation

protocol SomeDelegateProtocol : class {
    func firstFunc() -> String
    func secondFunc() -> Bool
    func thirdFunc() -> Self
}

class MyClass {
    weak var delegate : SomeDelegateProtocol?

tonyarnold

#if DEBUG
/**
 Toggles assertion of Core Data managed object contexts. Only available when DEBUG is defined.

 When enabled, your application will throw an exception when accessing or modifying entities in a context other than their own.
 */
void TCBToggleAssertingContextQueues();
#endif

andymatuschak

//
//  MultiDirectionAdjudicatingScrollView.swift
//  Khan Academy
//
//  Created by Andy Matuschak on 12/16/14.
//  Copyright (c) 2014 Khan Academy. All rights reserved.
//

import UIKit
import UIKit.UIGestureRecognizerSubclass

swizzlr

List of Block Declaration Syntaxes

Throughout, let

• return_type be the type of object/primitive/etc. you'd like to return (commonly void)
• blockName be the variable name of the block you're creating
• var_type be the type object/primitive/etc. you'd like to pass as an argument (leave blank for no parameters)
• varName be the variable name of the given parameter And remember that you can create as many parameters as you'd like.

Blocks as Variables

Possibly the most common for of declaration.

Tricertops

View → Design → Model

iOS applications are usually built with MVC (Model – View – Controller) architecture, which introduces very important concept of separating actual data (Model Layer) and their presentation (View Layer), while the application logic (Controller Layer) stands between them.

View ← Controller → Model

With MVC you typically write most of the code in UIViewController, which usually represents the Controller Layer. View Layer can be easily done in Interface Builder and Model Layer usually doesn’t need a lot of code. The UIViewControleler then holds strong references to both View and Model objects and is responsible for setting them up, handling actions and listening to events.

The problem is, that this middle layer tends to hold too much code and this situation is then jokingly called Massive View Controller. When a single class sets up views, formats data values, handles user input and actions, listens for a bunch of notif

jamztang

Copyright (c) 2013 Jamz Tang <jamz@jamztang.com>
 
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished
to do so, subject to the following conditions:
 
The above copyright notice and this permission notice shall be included in all

subdigital

// Property Nonatomic Strong
// Platform: All
// Completion Scopes: ClassInterfaceMethods

@property (nonatomic, strong) <# class_name #> *<# variable_name #>;

jspahrsummers

Simple visual illustrations of how CGRectDivideWithPadding works.

Slicing from CGRectMinXEdge

  +-------+---------+------------>
e |       |         |
d | slice | padding | remainder…
g |       |         |
e |       |         |

rjw57

/* CGSPrivate.h -- Header file for undocumented CoreGraphics stuff. */

/* This file is a relicensed portion of DesktopManager and was originally released under
 * the terms of the GNU General Public Licence. Original licence text follows the new terms.
 * The contents of this file has been re-released by the original author under the following terms:
 *
 * Copyright (C) 2003, 2004, 2013 Richard J Wareham <richwareham@users.sourceforge.net>
 *
 * Permission is hereby granted, free of charge, to any person obtaining a copy of this
 * software and associated documentation files (the "Software"), to deal in the Software