// dependencies.gradle
ext.versions = [
code : 1,
name : '1.0',
minSdk : 16,
targetSdk : 26,
import android.content.ClipData | |
import android.graphics.Paint | |
import android.os.Build | |
import android.os.Bundle | |
import android.support.v4.view.* | |
import android.support.v4.view.accessibility.AccessibilityNodeInfoCompat | |
import android.support.v4.view.accessibility.AccessibilityNodeProviderCompat | |
import android.view.* | |
/** |
git ls-files -z myFolderToIgnore/ | xargs -0 git update-index --assume-unchanged |
State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?
There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.
Here I present a composable pattern for pure state machiness with effects,
/* | |
* Hex Opacity Values | |
*/ | |
100% — FF | |
95% — F2 | |
90% — E6 | |
85% — D9 | |
80% — CC | |
75% — BF |
package com.example.rx_okhttp; | |
import com.squareup.okhttp.OkHttpClient; | |
import org.apache.http.*; | |
import org.apache.http.entity.InputStreamEntity; | |
import org.apache.http.message.BasicHeader; | |
import org.apache.http.message.BasicHttpResponse; | |
import rx.Observable; | |
import rx.Observer; | |
import rx.Scheduler; |
/* Copyright 2013 Google Inc. | |
Licensed under Apache 2.0: http://www.apache.org/licenses/LICENSE-2.0.html */ | |
package com.example.latlnginterpolation; | |
import android.animation.ObjectAnimator; | |
import android.animation.TypeEvaluator; | |
import android.animation.ValueAnimator; | |
import android.annotation.TargetApi; | |
import android.os.Build; |
import javafx.application.Application; | |
import static javafx.application.Application.launch; | |
import javafx.event.ActionEvent; | |
import javafx.event.EventHandler; | |
import javafx.scene.Scene; | |
import javafx.scene.control.Button; | |
import javafx.scene.control.ScrollPane; | |
import javafx.scene.image.Image; | |
import javafx.scene.image.ImageView; | |
import javafx.scene.layout.Pane; |
10/08/2012 | |
- Adicionada opção para o formato 0XX11987654321, com ou sem zero no sufixo (Contribuição: Carlos Luizetto / Roberto Akama) | |
- Adicionada verificação da "gem vcard" para os casos em que o componente responsável pela leitura e edição de vCards não está instalado | |
02/08/2012 | |
- Correção de bugs | |
- Lista de prefixos da Nextel (SME/trunking não faz parte da mudança) (Contribuição: Maurício Iwata) | |
- Adição do formato 9-XXXX-XXXX (Contribuição: Carlos Luizetto) | |
Movies Recommendation:
- MovieLens - Movie Recommendation Data Sets http://www.grouplens.org/node/73
- Yahoo! - Movie, Music, and Images Ratings Data Sets http://webscope.sandbox.yahoo.com/catalog.php?datatype=r
- Jester - Movie Ratings Data Sets (Collaborative Filtering Dataset) http://www.ieor.berkeley.edu/~goldberg/jester-data/
- Cornell University - Movie-review data for use in sentiment-analysis experiments http://www.cs.cornell.edu/people/pabo/movie-review-data/
Music Recommendation:
- Last.fm - Music Recommendation Data Sets http://www.dtic.upf.edu/~ocelma/MusicRecommendationDataset/index.html