Joan Llenas joanllenas

Talking about Toys

Every year Santa 🎅 brings joy (and presents 🎁) to all the kids in the world. Well, not when I was a child! Following the usual Spanish traditions, the Three Reyes Magos brought me presents in their camels 🐫 following the Star 💫 Nowadays, it's Sinterklaas who puts pepernoten in my shoes 👞. Because in fact there's not one, but a group of present-bringing people, distributed across the globe 🌐, each with their own part of the world to cover (or you really thought just one man and eight reindeers could do it all by their own?)

In order to communicate, they need a way to exchange information about presents. Since they are all very wise, they've agreed to use Haskell, so this information is represented using algebraic data types. Here are some types related to building blocks:

data Block = Block BlockBrand String Color
data BlockBrand = Lego | KNex

@ngrx/store v3

Problems:

Users want to compose reducer tree across modules
Idea of a single reducer function makes it difficult for the library to dynamically augment the shape of the state tree
Turning control over to the library to build the root reducer limits the use of meta-reducers
Feature modules may inadvertently collide with the state of the root module
Library authors may want to leverage @ngrx/store in their projects and provide an easy way

type below:

brew update
brew install redis

To have launchd start redis now and restart at login:

brew services start redis

Comprehensive Introduction to @ngrx/store

By: @BTroncone

Also check out my lesson @ngrx/store in 10 minutes on egghead.io!

Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!

Table of Contents

Should be work with 0.18

Destructuring(or pattern matching) is a way used to extract data from a data structure(tuple, list, record) that mirros the construction. Compare to other languages, Elm support much less destructuring but let's see what it got !

Tuple

myTuple = ("A", "B", "C")
myNestedTuple = ("A", "B", "C", ("X", "Y", "Z"))

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

Learning FP the hard way: Experiences on the Elm language

by Ossi Hanhinen, @ohanhi

with the support of Futurice 💚.

Licensed under CC BY 4.0.

	module GameState
	exposing
	( Game(..)
	, GameDefinition
	, PlayState
	, loading
	, updateGameDefinition
	, updatePlayState
	, updateScore
	, toReady

	<ng-template ngFor let-resource [ngForOf]="resources">
	<li>
	<button (click)="resource.expanded = !resource.expanded">Open</button>
	</li>
	<li *ngIf="resource.expanded">
	Something fancy here
	</li>
	</ng-template>

	elm-stuff/
	*.js