public
Rubygem
Description: A rails plugin that simulates some of the old scaffold funcionality, but using RESTful controllers, will_paginate for pagination and enforces the model first approach
Homepage: http://www.urubatan.info/tag/mydry/
Clone URL: git://github.com/urubatan/mydry.git
Click here to lend your support to: mydry and make a donation at www.pledgie.com !
mydry /
name age message
file .gemified Tue Apr 22 10:55:50 -0700 2008 added gemify to turn the plugin into a gem, sin... [urubatan]
file MIT-LICENSE Loading commit data...
file Manifest.txt
file README Wed Feb 20 09:10:56 -0800 2008 readme updated [Rodrigo Urubatan Ferreira Jardim]
file Rakefile Wed Feb 20 09:02:19 -0800 2008 initial commit [Rodrigo Urubatan Ferreira Jardim]
directory generators/
file init.rb
file install.rb
directory lib/ Thu Apr 24 10:45:39 -0700 2008 refactoring and DRY [urubatan]
file mydry.gemspec Sat Apr 26 09:55:27 -0700 2008 gem dependency fix [urubatan]
directory tasks/ Wed Feb 20 09:02:19 -0800 2008 initial commit [Rodrigo Urubatan Ferreira Jardim]
directory test/ Wed Feb 20 09:02:19 -0800 2008 initial commit [Rodrigo Urubatan Ferreira Jardim]
file uninstall.rb
Mydry
=====

This plugin emulates some of the old "scaffold" functionality, but using RESTFul controllers, will_paginate for 
pagination, partials for forms and enforces the model first approach.

The basic workflow is this:
1 - create a migration and define your initial table
2 - ./script/generate drymodel model_name
  here the model file generated for you, will have all the validations and belongs defined in the database table
  you can add more validations, configure relationships, code your model
3 - ./script/generate dryscaffold model_name
  here the scaffold will import the model definition (currently it is working with the database, but the next release 
  will import from the model), and generate all the boilerplate code for you.


The origin of this plugin was the need to define a validation in the migration (Eg.: :null => false), in the model again 
(Eg.: validates_presence_of :column), then again in the view, ...
The way this generators work I define one thing once and it is generated in the other places for me.


Example
=======

Example goes here.


Copyright (c) 2008 Rodrigo Urubatan Ferreira Jardim, released under the MIT license