pk

#import "SenTestCase+MethodSwizzling.m"

@interface ExampleTest : SenTestCase {}
+ (BOOL)trueMethod;
+ (BOOL)falseMethod;
@end

@implementation ExampleTest

+ (BOOL)trueMethod  { return YES; }

brendanjerwin

-(void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender {
    DDLogVerbose(@"prepareForSegue: %@", segue.identifier);

    SEL selector = NSSelectorFromString([NSString stringWithFormat:@"%@ToController:WithSegue:", segue.identifier]);
    if ([self respondsToSelector:selector]) {
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Warc-performSelector-leaks"
        [self performSelector:selector withObject:segue.destinationViewController withObject:segue];
#pragma clang diagnostic pop
    } else {

eternalstorms

UI- and App Frameworks Evangelist - Jake Behrens, behrens@apple.com, twitter: @Behrens
	- What's new in Cocoa
	- Accessibility in iOS
	- Building User Interfaces for iOS 7
	- Getting Started with UIKit Dynamics
	- What's new in Cocoa Touch
	- What's New With Multitasking
	- Best Practices for Cocoa Animation
	- Improving Power Efficiency with App Nap
	- Introducing Text Kit

bastibense

How to fix blurry fonts on some external monitors when using MacBook Pro Retina

It seems that graphcis and fonts look rather blurry on some monitors when hooked up to a MacBook Pro (Retina). This might fix the issue for you:

1. Download patch-edid.rb from http://embdev.net/attachment/168316/patch-edid.rb

2. Execute in Terminal (without the $):

   $ ruby patch-edid.rb

3. Copy produced folder (example: DisplayVendorID-22f0) to /System/Library/Displays/Overrides (authorize if needed, if the folder exists, backup it before)

nicklockwood

Storyboard Segues initially seem like a pretty cool way to construct interfaces using minimal glue code. But actually, ordinary nibs already support this, and in a much more flexible way.

Certainly, a Storyboard lets you bind a button action up to display a view controller with no code, but in practice you will usually want to pass some data to the new controller, depending on which button you used to get there, and this means implementing the -prepareForSegue:sender: method, which rapidly becomes a giant if/elseif statement of doom, negating most of the benefit of the codeless segue:

- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender
{
    if ([segue.identifier isEqualToString:@"modalSegue"])
    {
        ModalViewController *controller = (ModalViewController *)segue.destination;

controller.someProperty = someValue;

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];
}

danielfilho

Validação para cartão de crédito.

Bin e padrões para validação de cartão de crédito.

Bandeira	Comeca com	Máximo de número	Máximo de número cvc
Visa	4	13,16	3
Mastercard	5	16	3
Diners	301,305,36,38	14,16	3

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.

chriseidhof

import UIKit

struct Screen<A> {
    let run: (A -> ()) -> UIViewController
}

struct Step<A> {
    let build: (navigationController: UINavigationController, callback: A -> ()) -> UIViewController
}

miguelbassila

class PersonBuilder {

  private final var name: String
  private final var age: String?
  private final var gender: String?

  init(name: String) {
    self.name = name
  }