dmarcato

def toCamelCase(String string) {
    String result = ""
    string.findAll("[^\\W]+") { String word ->
        result += word.capitalize()
    }
    return result
}

afterEvaluate { project ->
    Configuration runtimeConfiguration = project.configurations.getByName('compile')

lgvalle

public class FacebookHomeProvider {
	protected final PublishSubject<FbPost> behaviorSubject;
	private Request request;

	public FacebookHomeProvider() {
		behaviorSubject = PublishSubject.create();
		behaviorSubject.subscribeOn(Schedulers.io());
	}

    /**

balysv

import android.content.Context;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.BaseAdapter;

import java.util.Collection;
import java.util.concurrent.atomic.AtomicInteger;

import rx.Observable;

f2prateek

/*
 * Copyright 2014 Prateek Srivastava
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *    http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

devunwired

/**
 * An example of adding these transitions to a Fragment.  This simple
 * version just applies opposite transitions to any Fragment whether it is
 * entering or exiting view.  You can also inspect the transit mode parameter
 * (i.e. TRANSIT_FRAGMENT_OPEN, TRANSIT_FRAGMENT_CLOSE) in combination to do
 * different animations for, say, adding a fragment versus popping the back stack.
 * 
 * Transactions without an explicit transit mode set, in this example, will not
 * animate.  Allowing the initial fragment add, for example, to simply appear.
 */

mkuprionis

Copied from Cyril Mottier's post on G+

His comments:

In order to implement tabs I decided to go for an entirely custom solution. I created the tab bar from scratch and added it as a custom ActionBar View. The tabs container is called TabBarView and extends LinearLayout. TabBarView actually handles the "selection strip".

The TabBarView is then filled with several TabView (one for each tab). The main purpose of TabView is to provide a nice API to deal with icon and the optional text (only visible in landscape) and handle the long press gesture (long pressing a tab displays a hint).

Once the TabBarView is initialized with a bunch of TabView, it is added as a custom View to the ActionBar:

lgvalle

public class HomePresenterImpl implements HomePresenter {
	private static final String TAG = HomePresenterImpl.class.getSimpleName();
	private final HomeScreen screen;
	private final DataProvider provider;
	private Subscription subscription1;

	public HomePresenterImpl(HomeScreenImpl screen, DataProvider dataProvider) {
		this.screen = screen;
		this.provider = dataProvider;
	}

fappel

import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

@Retention( RetentionPolicy.RUNTIME )
@Target( {
  java.lang.annotation.ElementType.METHOD
} )
public @interface Repeat {
  public abstract int times();

xrigau

<?xml version="1.0" encoding="utf-8"?>
<manifest
  xmlns:android="http://schemas.android.com/apk/res/android"
  package="com.novoda.espresso">
  
  <!-- For espresso testing purposes, this is removed in live builds, but not in dev builds -->
  <uses-permission android:name="android.permission.SET_ANIMATION_SCALE" />

  <!-- ... -->
  

JakeWharton

import android.text.SpannableStringBuilder;
import java.util.ArrayDeque;
import java.util.Deque;

import static android.text.Spanned.SPAN_INCLUSIVE_EXCLUSIVE;

/** A {@link SpannableStringBuilder} wrapper whose API doesn't make me want to stab my eyes out. */
public class Truss {
  private final SpannableStringBuilder builder;
  private final Deque<Span> stack;