Something summary

Updated for Ruby 2.X This is a packaged version of CSVScan, written by MoonWolf. If you can read Japanese, checkout README.ja for whatever he said. On a 10,000 line file: time cat example.csv | ruby fastercsv_benchmark.rb real 0m8.804s user 0m8.502s sys 0m0.304s time cat example.csv | ruby csvscan_benchmark.rb real 0m0.860s user 0m0.782s sys 0m0.088s

SEO friendly permalinks for your Active Record models

Batch edit passwords for domains managed at [http://access.enom.com](http://access.enom.com)

Provides the ActiveRecord helper method <tt>named_scope_for_time_attr</tt>. Given the name of a time attribute of an ActiveRecord model (e.g. <tt>created_at</tt> of <tt>Claim</tt>) it defines a correspondent named scope for easy access to an arbitrarily time range (scope).

namelib is a Ruby fork of NameCase, a library for converting denormalized names to be properly cased.

A simple API wrapper for Nanowrimo.org. Nanowrimo Word Count API documentation here: http://www.nanowrimo.org/eng/wordcount_api

youtube-g is a pure Ruby client for the YouTube GData API. It provides an easy way to access the latest YouTube video search results from your own programs. In comparison with the earlier Youtube search interfaces, this new API and library offers much-improved flexibility around executing complex search queries to obtain well-targeted video search results. More detail on the underlying source Google-provided API is available at: http://code.google.com/apis/youtube/overview.html

production_log_analyzer lets you find out which actions on a Rails site are slowing you down. Bug reports: http://rubyforge.org/tracker/?func=add&group_id=1513&atid=5921

== DESCRIPTION: Need makes ruby relative requires just work. Simply need a file with a relative path and the file will always be required correctly, regardless of what file your application is being launched through. Typically, ruby projects would unshift lib onto $PATH or use the File.dirname(__FILE__) trick. Using need means you don't have to worry about either of these. Assume you have two files, one directly in lib and the other in lib/extensions. Let's assume that file_a in lib requires file_b, in lib/extensions. Previously, you would doing some crazy load path unshifting or use the __FILE__ trick to make these requires flexible enough to work when your app is being accessed by rake, through a test suite, or required as a gem. Now, just use need. In file_a: need{"extensions/file_b"} need "extensions/file_b"

This gem provides methods to access the needish.com api

A tool to verify javascript code without worrying about including javascript library.

Ruby wrapper to access No Kahuna (www.nokahuna.com) from within your Ruby projects.

Plugin for fine grain MySQL options in DataMapper

This is an application which helps you to manage a database for the Monte Carlo simulations. For the dtailed usage, see http://nera.rubyforge.com

Convert nested OpenStruct to Hash

Store and retrieve files on Gmail.

Backup files to Gmail.

Manages persistent connections using Net::HTTP plus a speed fix for Ruby 1.8. It's thread-safe too! Using persistent HTTP connections can dramatically increase the speed of HTTP. Creating a new HTTP connection for every request involves an extra TCP round-trip and causes TCP congestion avoidance negotiation to start over. Net::HTTP supports persistent connections with some API methods but does not handle reconnection gracefully. Net::HTTP::Persistent supports reconnection and retry according to RFC 2616.

Net::LDAP for Ruby (also called net-ldap) implements client access for the Lightweight Directory Access Protocol (LDAP), an IETF standard protocol for accessing distributed directory services. Net::LDAP is written completely in Ruby with no external dependencies. It supports most LDAP client features and a subset of server features as well. Net::LDAP has been tested against modern popular LDAP servers including OpenLDAP and Active Directory. The current release is mostly compliant with earlier versions of the IETF LDAP RFCs (2251–2256, 2829–2830, 3377, and 3771). Our roadmap for Net::LDAP 1.0 is to gain full <em>client</em> compliance with the most recent LDAP RFCs (4510–4519, plutions of 4520–4532).