wajahatkarim3

/**
 * Kotlin Extensions for simpler, easier and funw way
 * of launching of Activities
 */

inline fun <reified T : Any> Activity.launchActivity (
        requestCode: Int = -1,
        options: Bundle? = null,
        noinline init: Intent.() -> Unit = {}) 
{

wispborne

import java.util.concurrent.atomic.AtomicBoolean

/**
 * Wraps some data that should track when it has been viewed and allow future viewers to avoid a second showing.
 * Useful for showing messages in the app that auto-hide because this class can exist in the app's state.
 */
data class ViewOnceData<T>(private val data: T) {
    val wasViewed = AtomicBoolean(false)

    /**

internetmosquito

images_names = list()
for iterator, image_file in enumerate(images):
	image_path = os.path.join(folder_name, image_file)
	images_names.append(self.path_leaf(image_path))
	self.images_names.append(self.path_leaf(image_path))
	with open(image_path, 'rb') as image:
		image_content = base64.b64encode(image.read())
		image_payload = {}
		image_payload['image'] = {}
		image_payload['image']['content'] = image_content.decode('UTF-8')

vestrel00

// This is a super simplified example of how to use the new dagger.android framework
// introduced in Dagger 2.10. For a more complete, in-depth guide to dagger.android
// read https://proandroiddev.com/how-to-android-dagger-2-10-2-11-butterknife-mvp-part-1-eb0f6b970fd

// For a complete codebase using dagger.android 2.11-2.17, butterknife 8.7-8.8, and MVP,
// see https://github.com/vestrel00/android-dagger-butterknife-mvp

// This example works with Dagger 2.11-2.17. Starting with Dagger 2.11, 
// @ContributesAndroidInjector was introduced removing the need to define @Subcomponent classes.

yanngx

package be.brol

import android.os.Binder
import android.os.Bundle
import android.support.v4.app.BundleCompat
import android.support.v4.app.Fragment

/**
 * Eases the Fragment.newInstance ceremony by marking the fragment's args with this delegate
 * Just write the property in newInstance and read it like any other property after the fragment has been created

sockeqwe

class FooActivity extends MviActivity<...> {
   @Inject FooPresenter
     
   public void onCreate(Bundle bundle){
     super.onCreate(bundle);
     FooComponent component = DaggerFooComponent.builder()
        .fooModule(new FooModule(bundle))
        .build();
      
     component.inject(this);

iago-suarez

Setting Up OpenCL for OpenCV on Android, the full story

The tutorial Use OpenCL in Android camera preview based CV application show us how we can use the Transparent API to dramatically increase the performance of some expensive operations.

The first step in order to be able to execute the tutorial example is to re-compile opencv with the correct flags:

# Export your NDK, it will be looked for OpenCV to compile your project. In my case
export ANDROID_NDK=~/graffter/libs/android-ndk-r10d/

# Download the necessary code

lawloretienne

Table Of Contents

• Data Structures
  • Linked Lists
  • Trees
    • Binary Trees
    • Binary Search Tree
    • Red-Black Tree
    • AVL Tree
• Tries

andymatuschak

A composable pattern for pure state machines with effects

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,

iiredalert

<?xml version="1.0" encoding="utf-8"?>
<resources>

<!-- google's material design colours from 
http://www.google.com/design/spec/style/color.html#color-ui-color-palette -->

    <!--reds-->
    <color name="md_red_50">#FFEBEE</color>
    <color name="md_red_100">#FFCDD2</color>
    <color name="md_red_200">#EF9A9A</color>