Parses dry css files and generates conventional css

Don't repeat yourself translating over and over common words you use for your project. Translate them once, and then you'll be able to reuse them directly on the I18n yml file

Provides extensions to ActionView::Helpers::CaptureHelper: content_for_with_default, no_content_for, and an enhanced content_for that plays nice with friends

Helper and class methods for authlogic and declarative authorization, drying up the workflow.

Flatter transforms a deeply nested graph of ActiveModel-like objects to a single mapper object that handles all the nested attributes and has a very flexible behavior for handling validation, saving routines with a DRY approach.

# Gemspec Gemspec is a convention-over-configuration library for creating DRY ruby gems that are easy to rename and whose gemspec and scaffolded parts easy to reuse by simply copying them elsewhere.

Define WinAutomation procedures that can be included elsewhere without consistency issues.

Generating HTML tables of data in the views of your Rails application is not very DRY even for the simpler of cases. Cheveret allows you to more clearly separate logic and templating and reduce the amount of code in your views.

ActiveDryDeps not modify constructor and support Dependency Injection for modules. Also you can import method from any object in your container. Adding extra dependencies is easy and improve readability your code.

use formic to generate markup from sematic syntax. formic DRY your template and make it readable. It also seperate the sematic of the content from the actual markup, make it possible to render multiple view for the same content

Know how you can't just use 'form_for' in rails with a newly initialized ActiveResource object? Ever get annoyed at having to add default attributes to your newly initialized ActiveResource objects? Fortify gives you the power to DRY'ly define default attributes for your ActiveResource derived classes.

A pronto runner for Tailor - Swift code analyzer. Pronto runs analysis quickly by checking only the relevant changes. Created to be used on pull requests, but suited for other scenarios as well. Perfect if you want to find out quickly if branch introduces changes that conform to your styleguide, are DRY, don't introduce security holes and more.

Define serialization styles for your ActiveRecord models

DRY your controllers and make your API more predictable by defining responders for different formats. E.g. Posting an invalid resource in HTML should render a form with errors, while in JSON you expect serialized errors.

Binder allows you to evaluate a proc in a closure other than the one in which it was created. It also includes a method :bind to DRY up code for anyone creating a domain specific language.

DRY for Net::HTTP

A way to run JavaScript based on Rails controller actions. This gives you the freedom to DRY up your JavaScript, or modularize code around REST resources, whatever you can think of!

This module attempts to create structured view helpers. Essentially, a blockpile consists of a ruby class file, and a template. This allows for isolated blocks of view logic, that can maintain a clean separation of markup language from ruby code. Blocks can be inherited from to DRY up view logic.

Minimal, simple, DRY DSL for searching Elasticsearch. Takes one shallow hash argument and translates it to an elaborate one passed on to elasticsearch-api. The price: narrower options. The gain: succinctness. For example, a root <tt>:range</tt> is always a boolean filter and always includes the edges: tractor = Client.new opts = { range: { timestamp: ['now-5m', 'now'] } } tractor.search(opts) # => sends the following to Ealsticsearch: { "query": { "bool": { "filter": [ { "range": { "timestamp": { "gte":"now-5m", "lte":"now" } } } ], "must": [], } } }

Provides a some useful modules, classes, and methods as well as a DSL-like syntax for FFI::Struct layouts