Update the Readme about how to run the test suite
Fix before_validation :xxx, :on => :create
Require only what is needed
Restart from scratch
Version bump to 0.0.0
Beginning the Gem management with Jeweler
Separate core extensions into a specific file
Extend AR::Base with Geokit::ActsAsMappable using AS::Concern

For the moment, we must "include Geokit::ActsAsMappable" in ActiveRecord
subclasses to be ble to use "acts_as_mappabe()".
Maybe its good thing to explicitly extend objects with modules.
It's often seen in other recent libs (AR with ActiveModel components, MongoID,
MongoMapper, …)
Add a placeholder for a future Railtie
Delete ignored files/folders
Update gemspec
Use a "glue" module to include ActsAsMappable into AciveRecord

This adds only this method to all the models (with the Railtie initializer).
Calling it includes the rest of ActsAsMappable into the model
Rename the gem to geokit_rails

It will be easier to have some config keys, … if tere is no dash in the name.
There is still a lib/geokit-rails.rb for "historic" compatibility (is it really needed ?)
Default settings for Geokit are back
Adapters are back
GeocoderControl is back

It is included in ActionController in the Railtie
IpGeocodeLookup is back
Rename the gem in the Rakefile
Configuration can be done in environment files or initializer
Renaming the gem was stupid ; let's revert this