billburgess

MyClass.h

#import "AnotherClass.h"

@interface MyClass : NSObject <AnotherClassDelegate>

+(void)myMethod;

MyClass.m

billburgess

I realize that the decision has been mostly made regarding our future in version control systems. And while I think SVN is definitely a big step in the right direction… I feel we could make an even bigger step in this direction with Git. I will admit that I am biased towards Git, I am not alone in my admiration for it. I would like to outline a few thoughts for consideration. I will support whichever direction we take, but would like to offer my own opinions and research on the matter.

* SVN creates .svn directories in every single folder (much like CVS). Every script we write or update to our new found frameworks we use will have to handle this. We can't currently swap out a framework once it has been added to CVS for a newer version without breaking the version control for it. This will hold true for any upgrade to SVN.

* In SVN, each file & folder can come from a different revision or branch. At first, it sounds nice to have this freedom. But what this actually means is that there is a million different 

billburgess

// store user/pass to the keychain
KeychainItemWrapper *wrapper = [[KeychainItemWrapper alloc] initWithIdentifier:@"SomeCustomIdentifier" accessGroup:nil];
[wrapper setObject:APP_NAME forKey:(__bridge id)kSecAttrService];
[wrapper setObject:(__bridge id)kSecAttrAccessibleAlways forKey:(__bridge id)kSecAttrAccessible];
[wrapper setObject:email forKey:(__bridge id)kSecAttrAccount];
[wrapper setObject:token forKey:(__bridge id)kSecValueData];