desandro

Re: On layout & web performance by Kelly Norton

#lazyweb Is there any documentation about which jQuery functions/effects trigger layout? re: kellegous.com/j/2013/01/26/l…

— Dave Rupert (@davatron5000) January 28, 2013

<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

getWidthOrHeight() used in jQuery.fn.width/height

clientLeft

• 3180 jQuery.event.mousehooks.filter

dergachev

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

joefiorini

<div class="header-wrapper">
  <header class="group">
    <h1>Style Tile<br>Template</h1>
    <hgroup class="project-title">
      <h2>Project name</h2>
      <h3>Style tile</h3>
      <h4>Version 1</h4>
    </hgroup>
  </header>
</div>

henrik

1. Your class can be no longer than 100 lines of code.
2. Your methods can be no longer than five lines of code.
3. You can pass no more than four parameters and you can’t just make it one big hash.
4. When a call comes into your Rails controller, you can only instantiate one object to do whatever it is that needs to be done. And your view can only know about one instance variable.

You can break these rules if you can talk your pair into agreeing with you.

concerning.rb

class Module
  # We often find ourselves with a medium-sized chunk of behavior that we'd
  # like to extract, but only mix in to a single class.
  #
  # We typically choose to leave the implementation directly in the class,
  # perhaps with a comment, because the mental and visual overhead of defining
  # a module, making it a Concern, and including it is just too great.
  #
  #
  # Using comments as lightweight modularity:

ndarville

Business Models

Advertising

Models	Examples
Display ads	Yahoo!
Search ads	Google

nzakas

/*
 * This is just an experiment. Don't read too much into the fact that these are global variables.
 * The basic idea is to combine the two steps of defining a constructor and modifying a prototype
 * into just one function call that looks more like traditional classes and other OO languages.
 */

// Utility function
function mixin(receiver, supplier) {

    if (Object.getOwnPropertyDescriptor) {

nickawalsh

@import compass

$icons: sprite-map("icons/*.png")
$icons-hd: sprite-map("icons-hd/*.png")

i
  background: $icons
  display: inline-block
  @media (-webkit-min-device-pixel-ratio: 1.5), (min-resolution: 144dpi)
    background: $icons-hd

ryanb

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article < ActiveRecord::Base

mason-stewart

// This is a peek behind the curtain at @zaarly's epic-fantasy-heavy-metal-themed internal styleguide, better known as Hammer.
//
// With this, you can add the .fancy class to a symbolset span inside of a heading tag to add a nice circular background. 
// Some adjustments to the positioning of a particular glyph may be necessary. 
// Each :before is set to postion: relative, so fine-tuning a .fancy glyph is simple, and won't affect the position of the circle.
//
// Example markup (in HAML):
// %h1
//   %span.ss-check.fancy
//   Cool Guy Settings™ saved!