kdabir

This script is created as an example to show how easy it is to use gstorm to crunch and consume data from rest apis.

Usage

Either download the script and run:

groovy ghstarred.groovy <your_github_id>

Or hotload it:

17twenty

a simple git branching model

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

The gist

numo16

#define ApplicationDelegate                 ((AppDelegate *)[[UIApplication sharedApplication] delegate])
#define UserDefaults                        [NSUserDefaults standardUserDefaults]
#define NotificationCenter                  [NSNotificationCenter defaultCenter]
#define SharedApplication                   [UIApplication sharedApplication]
#define Bundle                              [NSBundle mainBundle]
#define MainScreen                          [UIScreen mainScreen]
#define ShowNetworkActivityIndicator()      [UIApplication sharedApplication].networkActivityIndicatorVisible = YES
#define HideNetworkActivityIndicator()      [UIApplication sharedApplication].networkActivityIndicatorVisible = NO
#define NetworkActivityIndicatorVisible(x)  [UIApplication sharedApplication].networkActivityIndicatorVisible = x
#define NavBar                              self.navigationController.navigationBar

hollance

Communicate between objects using channels

When you have two objects A and B, say two view controllers, that you want to have talk to each other, you can choose from the following options:

• NSNotificationCenter. This is anonymous one-to-many communication. Object A posts a notification to the NSNotificationCenter, which then distributes it to any other objects listening for that notification, including Object B. A and B do not have to know anything about each other, so this is a very loose coupling. Maybe a little too loose...

• KVO (Key-Value Observing). One object observes the properties of another. This is a very tight coupling, because Object B is now peeking directly into Object A. The advantage of KVO is that Object A doesn't have to be aware of this at all, and therefore does not need to send out any notifications -- the KVO mechanism takes care of this behind the scenes.

• Direct pointers. Object A has a pointer to Object B and directly sends it messages when something of interest h

bric3

#  _______ _     _                      _       _                                   _ 
# |__   __| |   (_)                    (_)     | |                                 | |
#    | |  | |__  _ ___    ___  ___ _ __ _ _ __ | |_    _ __ ___   _____   _____  __| |
#    | |  | '_ \| / __|  / __|/ __| '__| | '_ \| __|  | '_ ` _ \ / _ \ \ / / _ \/ _` |
#    | |  | | | | \__ \  \__ \ (__| |  | | |_) | |_   | | | | | | (_) \ V /  __/ (_| |
#    |_|  |_| |_|_|___/  |___/\___|_|  |_| .__/ \__|  |_| |_| |_|\___/ \_/ \___|\__,_|
#                                        | |                                          
#                                        |_|                                          
#
# New home : https://github.com/bric3/osx-jdk5-installer

noahcampbell