Permalink
Commits on Mar 10, 2013
  1. Updated gemspec and version bump to 1.2.0

    Version numbers are now following DataMapper official versions.
    committed Mar 10, 2013
  2. Updated Rakefile

    committed Mar 10, 2013
  3. Improved README

    committed Mar 10, 2013
  4. updated .gitignore

    committed Mar 10, 2013
  5. Added Guardfile

    committed Mar 10, 2013
  6. Added Gemfile

    committed Mar 10, 2013
  7. Removed unwanted files

    committed Mar 10, 2013
Commits on Jun 9, 2010
  1. DM 1.0.0 compatibility

    committed Jun 9, 2010
  2. Version bump to 0.0.9

    committed Jun 9, 2010
Commits on Jun 8, 2010
  1. Updated gemspec

    committed Jun 8, 2010
  2. Version bump to 0.0.8

    committed Jun 8, 2010
  3. Updated README

    committed Jun 8, 2010
  4. Removed all forms of dependencies

    This was due to DM 1.0.0.rc3  issues seemingly.
    committed Jun 8, 2010
Commits on May 20, 2010
  1. updated gemspec

    committed May 20, 2010
  2. Version bump to 0.0.7

    committed May 20, 2010
  3. [Fix] Remove requirement for 'dm-more' 


    Minor cleanups
    committed May 20, 2010
Commits on Dec 20, 2009
  1. Bump version and updated spec

    committed Dec 20, 2009
  2. Version bump to 0.0.6

    committed Dec 20, 2009
  3. FIX: Now supports setting dynamic value field

    Just for those cases, when the value you want to collect and display is NOT the :id of the table, you can now define the field to use.
    
       is :select, :name, :value_field => :country_code 
    
    
    The results array would then be returned like this:
    
    	[:country_code, :name]
    committed Dec 20, 2009
Commits on Oct 30, 2009
  1. Version bump to 0.0.5

    committed Oct 30, 2009
  2. Version bump to 0.0.4

    committed Oct 30, 2009
  3. Changed the output order [value, key] of the output options array.

    Prior to this change the following was output:
    
    ['Letter A', 1]
    ['Letter B', 2]
    
    After this change the order is reversed:
    
    [1, 'Letter A']
    [2, 'Letter B']
    
    This is a more logical order since the option tag is formatted like this:
    
    <option value="1">Letter A</option>
    
    GOTCHA!
    
    When iterating through the resultant output, just remember to reverse the order of your args like this:
    
    	Category.items_for_select_menu.each do |value, key|....
    committed Oct 30, 2009
Commits on Aug 20, 2009
  1. Bump version

    committed Aug 20, 2009
  2. Ignoring doc/ dir

    committed Aug 20, 2009
  3. Version bump to 0.0.3

    committed Aug 20, 2009
  4. Added support for custom SQL queries.

    Now respects this:
    
      Category.items_for_select_menu(:publish_status => "on", :order => [ :id.desc ] )
    committed Aug 20, 2009