ssokolow

#!/usr/bin/env python
# -*- coding: utf-8 -*-
"""[application description here]"""

__appname__ = "[application name here]"
__author__  = "Stephan Sokolow (deitarion/SSokolow)"
__version__ = "0.0pre0"
__license__ = "GNU GPL 3.0 or later"

import logging

aaronpowell

#Installs a package into all projects in the solution (note: Requires NuGet 1.1+)
Get-Project -All | Install-Package packageName

manadart

namespace TinyIoCDemo
{
    // This is the interface for my aspect - the dependency for my classes.
    public interface IAspectDependency
    {
        string GetGreeting();
    }

    // And here is an implementation.
    public class GreetingAspect : IAspectDependency

chrishulbert

-(UIView *)tableView:(UITableView *)tableView viewForHeaderInSection:(NSInteger)section {
	UILabel *lbl = [[[UILabel alloc] init] autorelease];
	lbl.textAlignment = UITextAlignmentCenter;
	lbl.font = [UIFont fontWithName:@"Helvetica-Bold" size:18];
	lbl.text = @"My Centered Header";
	lbl.textColor = [UIColor whiteColor];
	lbl.shadowColor = [UIColor grayColor];
	lbl.shadowOffset = CGSizeMake(0,1);
	lbl.backgroundColor = [UIColor colorWithPatternImage:[UIImage imageNamed:@"my_head_bg"]];
	lbl.alpha = 0.9;

dhoerl

Reloading the NIB is expensive. Better to load it once, then instantiate the objects when you need a cell. Note that you can add UIImageViews etc to the nib, even multiple cells, using this method (Apple's "registerNIB" iOS5 allows only one top level object - one UITableViewCell. Bug 10580062 "iOS5 tableView registerNib: overly restrictive"

So my code is below - you read in the NIB once (in +initialize like I did or in viewDidload - whatever. From then on, you instantiate the nib into objects then pick the one you need. This is much more efficient than loading the nib over and over.

tmdvs

What Apple gives you and will cause a crash as dequeueReusableCellWithIdentifier: can't return a cell as none have ever been initialised.

- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath
{
    static NSString *CellIdentifier = @"Cell";
    UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];
       
    return cell;
}

keyboardsurfer

# Copyright: Benjamin Weiss (keyboardsurfer) https://github.com/keyboardsurfer
# Under CC-BY-SA V3.0 (https://creativecommons.org/licenses/by-sa/3.0/legalcode)

# built application files
*.apk
*.ap_
*.jar
!gradle/wrapper/gradle-wrapper.jar

# lint folder

andreynovikov

// Custom interface that enables communication between Fragment and its Activity
public interface OnItemSelectedListener
{
	public void onItemSelected(String item);
}

romainpiel

Sexy transition between Activities (based on Twitter transition)

Looking at the officiel Twitter Android client I've noticed the slight cool & sexy transition between activities. I was curious to know how that worked so I had fun with android xml animations and ended up with that:

push_left_in.xml

<?xml version="1.0" encoding="utf-8"?>
<set xmlns:android="http://schemas.android.com/apk/res/android">
<translate

baphillips

NSString* string = @"Hello World"; 

UIFont *font = [UIFont fontWithName:@"Helvetica-BoldOblique" size:21];

CGSize constraint = CGSizeMake(300,NSUIntegerMax);

NSDictionary *attributes = @{NSFontAttributeName: font};

CGRect rect = [string boundingRectWithSize:constraint 
                                   options:(NSStringDrawingUsesLineFragmentOrigin|NSStringDrawingUsesFontLeading)