Ronny Haase ronnyhaase

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets

Trello CSS Guide

“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”

You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

	// assertions/compareScreenshot.js
	var resemble = require('resemble'),
	fs = require('fs');

	exports.assertion = function(filename, expected) {
	var screenshotPath = 'test/screenshots/',
	baselinePath = screenshotPath + 'baseline/' + filename,
	resultPath = screenshotPath + 'results/' + filename,
	diffPath = screenshotPath + 'diffs/' + filename;

	<script type="text/javascript">
	(function () {
	"use strict";
	// once cached, the css file is stored on the client forever unless
	// the URL below is changed. Any change will invalidate the cache
	var css_href = './index_files/web-fonts.css';
	// a simple event handler wrapper
	function on(el, ev, callback) {
	if (el.addEventListener) {
	el.addEventListener(ev, callback, false);

	function isRetina() {
	//
	// The easy way, a handy little property in the global scope
	//
	if ( 'devicePixelRatio' in window )
	return window.devicePixelRatio >= 1.92;

	//
	// The hard way, via Media Queries
	//

	#!/usr/bin/env node

	// Reads JSON from stdin and writes equivalent
	// nicely-formatted JSON to stdout.

	var stdin = process.stdin,
	stdout = process.stdout,
	inputChunks = [];

	stdin.resume();

	@media (min--moz-device-pixel-ratio: 1.5),
	(-o-min-device-pixel-ratio: 3/2),
	(-webkit-min-device-pixel-ratio: 1.5),
	(min-device-pixel-ratio: 1.5),
	(min-resolution: 1.5dppx) {

	/* "retina" styles */

	}

	# Solution from http://www.jamiepenney.co.nz/2011/09/23/testing-content_for-in-rails-3-x-helpers-with-rspec/

	describe ApplicationHelper do
	describe "title" do
	it "should return an h2 tag with the given title" do
	helper.title("Lorem Ipsum")
	helper.content_for(:page_title).should eql "<h2>Lorem Ipsum</h2>"
	end

	it "should return the supplied block if a block was given" do

Ronny Haase ronnyhaase

Trello CSS Guide

Better local require() paths for Node.js

Problem

Possible solutions