chriseidhof

import Foundation

// A lens is a getter and a setter combined
struct Lens<Whole, Part> {
    let get: (Whole) -> Part
    let set: (inout Whole, Part) -> ()
}

// We can create a lens from a key path
extension Lens {

steventroughtonsmith

//
//  main.m
//  wwcd15sessionlister
//
//  Created by Steven Troughton-Smith on 10/06/2015.
//

#import <Foundation/Foundation.h>

int main(int argc, const char * argv[]) {

jarsen

extension RLMRealm {
    public func write(@noescape transaction: ()->()) {
        self.beginWriteTransaction()
        transaction()
        self.commitWriteTransaction()
    }
}

public struct Patient {
    public let info: ModelInfo

steventroughtonsmith

@interface UIWindow (resize)
-(void)_adjustSizeClassesAndResizeWindowToFrame:(CGRect)frame;
@end

typedef enum _UICustomRes
{
	UICustomResiPadTwoThirds,
	UICustomResiPadHalf,
	UICustomResiPadOneThird,
	UICustomResiPhone47,

nicklockwood

Suppose we want to add support for a new iOS 8 API in our framework that replaces an older iOS 7 API. There are a few problems we might face:

1. The new API will crash if we call it on iOS 7
2. The new API won't compile if we build it using the iOS 7 SDK
3. The old API will raise a deprecation warning if built with a deployment target of iOS 8 and up

These three problems require three different technical solutions:

1. We can avoid calling the new API on an old OS version by using runtime detection (e.g. respondsToSelector:)
2. We can avoid compiling new APIs on old SDKs using the __IPHONE_OS_VERSION_MAX_ALLOWED macro

nicklockwood

Hacking UIView animation blocks for fun and profit

In this article, I'm going to explore a way that we can create views that implement custom Core Animation property animations in a natural way.

As we know, layers in iOS come in two flavours: Backing layers and hosted layers. The only difference between them is that the view acts as the layer delegate for its backing layer, but not for any hosted sublayers.

In order to implement the UIView transactional animation blocks, UIView disables all animations by default and then re-enables them individually as required. It does this using the actionForLayer:forKey: method.

Somewhat strangely, UIView doesn't enable animations for every property that CALayer does by default. A notable example is the layer.contents property, which is animatable by default for a hosted layer, but cannot be animated using a UIView animation block.

steipete

- (NSString *)tableView:(UITableView *)tableView titleForSwipeAccessoryButtonForRowAtIndexPath:(NSIndexPath *)indexPath {
    return @"More";
}

- (void)tableView:(UITableView *)tableView swipeAccessoryButtonPushedForRowAtIndexPath:(NSIndexPath *)indexPath {
   NSLog(@"I wanted to be a pretty public API, but then time ran out and they forgot me...");

  // Hide the More/Delete menu.
  [self setEditing:NO animated:YES];
}

nicklockwood

# Mac OS X
*.DS_Store

# Xcode
*.pbxuser
*.mode1v3
*.mode2v3
*.perspectivev3
*.xcuserstate
project.xcworkspace/

matthiasplappert

@interface UIView (MPAdditions)
@end

@implementation UIView (MPAdditions)

- (id)debugQuickLookObject {
    if (self.bounds.size.width < 0.0f || self.bounds.size.height < 0.0f) {
        return nil;
    }
    

raven

<?xml version="1.0" encoding="UTF-8"?>
<Bucket
   type = "2"
   version = "2.0">
   <Breakpoints>
      <BreakpointProxy
         BreakpointExtensionID = "Xcode.Breakpoint.SymbolicBreakpoint">
         <BreakpointContent
            shouldBeEnabled = "Yes"
            ignoreCount = "0"