tenderlove

total gem count: 399
unique gem count: 90
2004-12: 1
2005-2: 2
2005-4: 3
2005-5: 3
2005-6: 3
2005-7: 4
2005-10: 2
2005-11: 3

stephencelis

# factory_girl for minitest
#
#   Factory.define :user do |f|
#     f.login 'johndoe%d'                          # Sequence.
#     f.email '%{login}@example.com'               # Interpolate.
#     f.password f.password_confirmation('foobar') # Chain.
#   end
#
#   Factory.define :post do |f|
#     f.user { Factory :user }                     # Blocks, if you must.

stephencelis

# More "proper" than a miniskirt (http://gist.github.com/273579).
class Minidress
  @@factories = {}
  class << self
    def define(name, &block)
      @@factories[name.to_s] = block
    end

    def build(name, attrs = {})
      new(name.to_s.classify.constantize.new, &@@factories[name.to_s]).record

sstephenson

# Pipe Ars Technica's live Apple event coverage into a Campfire room.
# http://arstechnica.com/apple/news/2010/01/tablet-live-event-liveblog.ars 
#
# Usage:
#   $ gem install -r hpricot tinder
#   $ ruby -rubygems ars_live.rb -ssl mysubdomain myroomid myapikey

require "hpricot"
require "open-uri"
require "tinder"

mislav

Pagination 101

Article by Faruk Ateş, [originally on KuraFire.net][original] which is currently down

One of the most commonly overlooked and under-refined elements of a website is its pagination controls. In many cases, these are treated as an afterthought. I rarely come across a website that has decent pagination, and it always makes me wonder why so few manage to get it right. After all, I'd say that pagination is pretty easy to get right. Alas, that doesn't seem the case, so after encouragement from Chris Messina on Flickr I decided to write my Pagination 101, hopefully it'll give you some clues as to what makes good pagination.

Before going into analyzing good and bad pagination, I want to explain just what I consider to be pagination: Pagination is any kind of control system that lets the user browse through pages of search results, archives, or any other kind of continued content. Search results are the o

pjb3

require 'benchmark'

puts
puts ENV["RUBY_VERSION"]

class A
  def initialize(foo)
    @foo = foo
  end
  def foo

octplane

require 'rubygems'
require 'mongo'

module MongoPubSub
  QUEUES_COLLECTION = 'queues'
  class EndSubscriptionException < Exception; end
  class Publisher
    def initialize(queue_name, mongo_connection)
      # Initialize queue collection as a capped collection
      if not mongo_connection[QUEUES_COLLECTION].collection_names.include?(queue_name)

jeffkreeftmeijer

FffuuuFormatter

A stupid RSpec formatter that prints FFFUUU instead of FFFFF. Heh.

Installation

Throw it in a file and run your specs like this:

$ rspec -r path/to/fffuuu_formatter.rb -f FffuuuFormatter spec/

bebraw

IMPORTANT! Remember to check out the wiki page at https://github.com/bebraw/jswiki/wiki/Game-Engines for the most up to date version. There's also a "notes" column in the table but it simply does not fit there... Check out the raw version to see it.

This table contains primarily HTML5 based game engines and frameworks. You might also want to check out the [[Feature Matrix|Game-Engine-Feature-Matrix]], [[Game Resources]] and [[Scene Graphs]].

Name	Size (KB)	License	Type	Unit Tests	Docs	Repository	Notes
Akihabara	453	GPL2, MIT	Classic Repro	no	API	github	Intended for making classic arcade-style games in JS+HTML5
AllBinary Platform	Platform Dependent	AllBinary	2D/2.5D/3D	n

matthewmccullough

##############################################################################
# History Configuration
##############################################################################
HISTSIZE=5000               #How many lines of history to keep in memory
HISTFILE=~/.zsh_history     #Where to save history to disk
SAVEHIST=5000               #Number of history entries to save to disk
#HISTDUP=erase               #Erase duplicates in the history file
setopt    appendhistory     #Append history to the history file (no overwriting)
setopt    sharehistory      #Share history across terminals
setopt    incappendhistory  #Immediately append to the history file, not just when a term is killed