Simple library to shorten the text by the specified length.

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`.

Ohnoes is a gem to report frontend errors using your existing backend error reporting.

OICFiscalPrinterLib is activex library for Novitus fiscal devices.

okuyama client for Ruby

Olag is Oren's set of utilities for creating a well-behaved gem. This is very opinionated software; it eliminates a lot of the boilerplate, at the cost of making many decisions which may not be suitable for everyone (directory structure, code verification, codnar for documentation, etc.).

olddoc contains old-fashioned document generators for those who do not wish to impose bloated, new-fangled web cruft on their readers.

Rails helper. Finds the irrelevent styles in your stylesheet and generates a html report to keep you informed.

A (very small) collection of Rake tasks for working with Omeka plugins.

OmniAuth strategy for Garmin

Omniauth lockitron strategy

OmniAuth strategy for Smashrun

An omniauth strategy for http://vocabulario.me

Omnidata let you define your model free from any specific database.

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'"

Create, read, update, and destroy Edmodo data via the One Eye API.

A Ruby library and cli tool that tries to identify mismatched names between Tock and Float

Everyone loves version control yeah? People also love to keep our business proposals organized. Why not have both? Using `one-pager` you can easily generate new one-pagers anywhere in your system. Simply run `$ one-pager init` in any directory and it will create a `docs/one-pagers` folder if it does not exist, as well as a `.one-pager` file if it already doesn't exist (this file is used for setting configurations). From here you can run commands such as `one-pager create "Allow users to purchase in DogeCoin"` and it will generate a markdown file (`doc/one-pagers/allow_users_to_purchase_in_dogecoin.md`), which will be pre-populated with with your one-pager template. This can be configured via the `.one-pager` file.