Merge pull request #14 from srbiv/master

set_table_name is deprecated in Rails 3.2
make concrete implementations independent

enables an application to have, for example, Features and
Settings, without sharing the `defaults` implementation.

in this way, Setler may be used to configure feature flags as
well as user-specific settings, which have differing needs.
Merge pull request #15 from coreyti/make_concrete_implementations_independent

make concrete implementations independent
Adds coreyti to contributors and version bump
Adds failing test for Issue#16
Switch to a class instance variable
Try another way of setting defaults
Kill trailing whitespace
Merge pull request #17 from stevenharman/remove_trailing_whitespace

Kill trailing whitespace
Rolls back change that broke old default behavior
Version bump
Use #update_attributes as #update_attribute is deprecated
Merge pull request #20 from stevenharman/use_update_attributes

Use #update_attributes as #update_attribute is deprecated in Rails 3.2.x
Version Bump
Use the class defined that inherits from Setler::Settings since it may have customizations on it

Customizations such as changing the database connection with dbcharmer.
Commenting out a failing test for unfixed functionality
Adding mocha to the development dependencies
Add a test for the new functionality to use the class that inherits from Setler::Settings
Adding pry
Check for a class being set in the ScopedSettings and use that if it's there