* oddb2tdat converts oddb.csv to oddb.dat * http://dev.ywesee.com/wiki.php/ODDB/Oddb2tdat

Open Drug Database for Switzerland. See the live version at http://ch.oddb.org

officetxt (Office.TXT) - the free writer's command line tool suite

== DESCRIPTION: My fork of aasmith's ofx-parser v1.0.2 and attempt at building the investment acct methods. OfxParser is a ruby library to parse a realistic subset of the lengthy OFX 1.x specification. == FEATURES/PROBLEMS: * Reads OFX responses - i.e. those downloaded from financial institutions and puts it into a usable object graph. * Supports the 3 main message sets: banking, credit card and investment accounts, as well as the required 'sign on' set. * Knows about SIC codes - if your institution provides them. See http://www.eeoc.gov/stats/jobpat/siccodes.html * Monetary amounts can be retrieved either as a raw string, or in pennies. * Supports OFX timestamps.

== DESCRIPTION: ofx-parser is a ruby library to parse a realistic subset of the lengthy OFX 1.x specification. == FEATURES/PROBLEMS: * Reads OFX responses - i.e. those downloaded from financial institutions and puts it into a usable object graph. * Supports the 3 main message sets: banking, credit card and investment accounts, as well as the required 'sign on' set. * Knows about SIC codes - if your institution provides them. See http://www.eeoc.gov/stats/jobpat/siccodes.html * Monetary amounts can be retrieved either as a raw string, or in pennies. * Supports OFX timestamps.

ObjectGraph will output Graphviz dot files of your objects in memory. It will ferret out your instance variables and enumerate over your enumerables to give you a graph of your object and its relationships. For sample output and more sample code see: * http://flickr.com/photos/aaronp/tags/graphviz/ * http://tenderlovemaking.com/2007/06/17/graphing-ruby-objects/ * http://tenderlovemaking.com/2007/01/13/graphing-objects-in-memory-with-ruby/

An API for OptionsHouse (http://optionshouse.com). Currently provides a mechanism for pulling stock and option quotes.

Add ANSI color codes to strings using a simple markup.

I'm tired of the complications that tools like bundler and rvm inject into my system and my workflow. I don't want 4 billion gems installed globally. I don't want to have `rake` slow down for no good reason. I don't want rvm to regress on undefined variables over and over and over (and I don't want to report it anymore when it does). I want as much simplicity as I can afford and still be able to get my job done. I've found pretty good balance using rbenv (only when needed) and by using this 45 line shell function `ohmygems` (aliased to `omg`, of course). I still have my system-level gems as my previous GEM_HOME gets moved into GEM_PATH so things like minitest and autotest are always available. But now I have private gems that are incredibly easy to switch around and only rely on simple environment variables to manage. To go back to normal, simply run `omg reset`.

OkExtensions by steved http://code.google.com/p/ok-extensions/ == DESCRIPTION: A set of extensions to the ruby stdlib

Safe arithmetic parser for Ruby apps

Test::Rails helps you build industrial-strength Rails code.

OmniFocus AtTask Integration

Plugin for omnifocus gem to provide bugzilla BTS synchronization. The first time this runs it creates a yaml file in your home directory for the bugzilla url, username, and queries. The queries config is optional. If it is not included bugzilla-omnifocus will pull all active bugs assigned to the specified user. To use a custom query or multiple queries you must include a queries parameter in your config. The queries config is an array of strings. Each string is the query string portion of the bugzilla search results url. Its easiest to create your search in bugzilla and then paste the portion of the url after the question mark into the config file. Example: --- bugzilla_url: http://bugs/buglist.cgi username: aja queries: ["bug_status=NEW", "bug_status=CLOSED"]

Plugin for omnifocus gem to provide rt BTS synchronization. The first time this runs it creates a yaml file in your home directory for the rt url, username, password, default queue and query. The query is optional. If you don't supply it omnifocus-rt will pull all tickets from the default queue assigned to the specified user. The use a custom query you must supply it in the config file. omnifocus-rt uses the REST interface to RT. More information about query formatting is available here: http://wiki.bestpractical.com/view/REST Example: :rt_url: rt :queue: QA :username: user :password: pass :query: "Queue='QA'ANDOwner='Nobody'ANDStatus!='rejected'"

Plugin for omnifocus gem to provide rubyforge BTS synchronization.

ETags are good, however normally they are generated based on strings. However, very often it is easier to pass in a complete model object as your ETag, or it's parametrized represenation (record id) together with the version. Or an array of objects (if you want to cache your object listing page and prevent it from spending time on template rendering). This module will take care of transforming any object into a stringified representation that is usable as an etag with minimum fuss.

Handy thing to ensure 100% test coverage for Ruby 1.9 projects

A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.

== FEATURES/PROBLEMS: * FIX (list of features or problems) == SYNOPSIS: FIX (code sample of usage) == REQUIREMENTS: