tclementdev

import SwiftUI

// This is an example of how to keep the ObservableObjects near the root of the view hierarchy
// and dispatch actions from any view easily without having to pass too many things down. This
// helps keep the views simple and makes previews a lot easier.
//
// This is inspired from what Apple is doing with `DismissAction`, `OpenURLAction`, `OpenWindowAction`, etc...


// The following is a very simple example with only two view-levels and we could pass closures directly,

jspahrsummers

/// Observes a run loop to detect any stalling or blocking that occurs.
///
/// This class is thread-safe.
@interface GHRunLoopWatchdog : NSObject

/// Initializes the receiver to watch the specified run loop, using a default
/// stalling threshold.
- (id)initWithRunLoop:(CFRunLoopRef)runLoop;

/// Initializes the receiver to detect when the specified run loop blocks for

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

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

austinzheng

import Foundation

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

class MyClass {
    weak var delegate : SomeDelegateProtocol?

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

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

depth42

@interface NSKeyedUnarchiver (Xcode5Fix)
@end

@implementation NSKeyedUnarchiver (Xcode5Fix)

+ (void)load
{
    [self exchangeInstanceMethod:@selector(decodeInt32ForKey:)
                      withMethod:@selector(xcode5Fix_decodeInt32ForKey:)];
}

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.

JaviSoto

#define MSDesignatedInitializer(__SEL__) __attribute__((unavailable("Invoke the designated initializer `" # __SEL__ "` instead.")))

// Sample usage:

- (instancetype)initWithObject:(id)object;
- (instancetype)init MSDesignatedInitializer(initWithObject:); // <- This even gets auto-complete.

// Now calling init on this class would throw a warning.