rails--rails/activesupport
Tarmo Tänav ef53d91516 Don't rely on string CoreExtensions in StringInquirer since it is sometimes expected to work before the core extension are loaded
Signed-off-by: David Heinemeier Hansson <david@loudthinking.com>
2008-10-30 17:48:32 +01:00
..
bin Simplify ActiveSupport::Multibyte and make it run on Ruby 1.9. 2008-09-21 17:21:30 +02:00
lib Don't rely on string CoreExtensions in StringInquirer since it is sometimes expected to work before the core extension are loaded 2008-10-30 17:48:32 +01:00
test Remove stuff that was deprecated in 2-1-stable 2008-10-21 11:34:56 +01:00
CHANGELOG Proper API for reloading translations 2008-10-29 10:51:56 +01:00
MIT-LICENSE Updated copyright years 2008-05-11 18:34:05 -05:00
README
Rakefile Proper update call for gem server 2008-10-23 20:29:25 +02:00
install.rb Fixed spelling errors (closes #9706) [tarmo/rmm5t] 2007-09-28 14:18:47 +00:00

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.