rails--rails/activesupport
Bryan Helmkamp 11db694e0b Remove cruft in the gem packaging and release code 2010-03-01 19:00:19 -08:00
..
bin
lib Optimize AS::Notifications to remember which subscribers don't match and not run them. This will allow notifications that are only useful in dev or testing to run efficiently in production. 2010-03-01 17:45:37 -08:00
test Optimize AS::Notifications to remember which subscribers don't match and not run them. This will allow notifications that are only useful in dev or testing to run efficiently in production. 2010-03-01 17:45:37 -08:00
CHANGELOG Use Object#singleton_class instead of #metaclass. Prefer Ruby's choice. 2010-02-25 09:32:29 -08:00
MIT-LICENSE Updating copyright dates on all licenses 2010-02-01 10:10:53 +11:00
README
Rakefile Remove cruft in the gem packaging and release code 2010-03-01 19:00:19 -08:00
activesupport.gemspec Bump i18n for new public I18n.normalize_keys 2010-02-25 15:06:11 -08:00
install.rb

README

= Active Support -- Utility classes and standard library extensions from Rails

Active Support is a collection of various utility classes and standard library extensions that were found useful
for Rails. All these additions have hence been collected in this bundle as way to gather all that sugar that makes
Ruby sweeter.


== Download

The latest version of Active Support can be found at

* http://rubyforge.org/project/showfiles.php?group_id=182

Documentation can be found at 

* http://as.rubyonrails.com


== Installation

The preferred method of installing Active Support is through its GEM file. You'll need to have
RubyGems[http://rubygems.rubyforge.org/wiki/wiki.pl] installed for that, though. If you have it,
then use:

  % [sudo] gem install activesupport-1.0.0.gem


== License

Active Support is released under the MIT license.


== Support

The Active Support homepage is http://www.rubyonrails.com. You can find the Active Support
RubyForge page at http://rubyforge.org/projects/activesupport. And as Jim from Rake says:

   Feel free to submit commits or feature requests.  If you send a patch,
   remember to update the corresponding unit tests.  If fact, I prefer
   new feature to be submitted in the form of new unit tests.

For other information, feel free to ask on the ruby-talk mailing list
(which is mirrored to comp.lang.ruby) or contact mailto:david@loudthinking.com.