1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
rails--rails/activesupport
2008-11-24 18:43:04 -08:00
..
bin Simplify ActiveSupport::Multibyte and make it run on Ruby 1.9. 2008-09-21 17:21:30 +02:00
lib Add config.preload_frameworks to load all frameworks at startup. Default to false so Rails autoloads itself as it's used. 2008-11-24 18:43:04 -08:00
test Explicitly require Builder in test that uses it 2008-11-24 11:05:54 -08:00
CHANGELOG Add ActiveSupport::MessageVerifier to aid users who need to store tamper-proof messages in cookies etc. 2008-11-23 15:33:59 +01:00
install.rb Fixed spelling errors (closes #9706) [tarmo/rmm5t] 2007-09-28 14:18:47 +00:00
MIT-LICENSE Updated copyright years 2008-05-11 18:34:05 -05:00
Rakefile Move sshpublisher require into the rake tasks that use it so ruby 1.9 and macruby don't need the rake gem installed 2008-11-08 18:58:08 -05:00
README Fix READMEs (closes #2680) [coffee2code] 2005-11-07 09:51:47 +00:00

= 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.