aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/README
diff options
context:
space:
mode:
authorFelix Dominguez <fdacat@me.com>2008-12-03 09:02:47 -0600
committerFelix Dominguez <fdacat@me.com>2008-12-03 09:02:47 -0600
commit601e40e744f44fe8819be100a8c472ea161d13ab (patch)
treef91214a9d6f854bbd9ff355d867d57e4ffcad503 /actionpack/README
parentecf52ba9af09af6c0423334878989ea5598bfb05 (diff)
downloadrails-601e40e744f44fe8819be100a8c472ea161d13ab.tar.gz
rails-601e40e744f44fe8819be100a8c472ea161d13ab.tar.bz2
rails-601e40e744f44fe8819be100a8c472ea161d13ab.zip
Updated Actionpack README. Removed reference to examples that have long since been removed from the distribution. Examples were removed by David on 09-09-07 in subversion changset 7424 http://dev.rubyonrails.org/changeset/7424
Diffstat (limited to 'actionpack/README')
-rw-r--r--actionpack/README17
1 files changed, 1 insertions, 16 deletions
diff --git a/actionpack/README b/actionpack/README
index 4d69103aa2..e4ce4aa044 100644
--- a/actionpack/README
+++ b/actionpack/README
@@ -373,21 +373,6 @@ new model). After creating the post, it'll redirect to the show page using
an URL such as /weblog/5 (where 5 is the id of the post).
-== Examples
-
-Action Pack ships with three examples that all demonstrate an increasingly
-detailed view of the possibilities. First is blog_controller that is just a
-single file for the whole MVC (but still split into separate parts). Second is
-the debate_controller that uses separate template files and multiple screens.
-Third is the address_book_controller that uses the layout feature to separate
-template casing from content.
-
-Please note that you might need to change the "shebang" line to
-#!/usr/local/env ruby, if your Ruby is not placed in /usr/local/bin/ruby
-
-Also note that these examples are all for demonstrating using Action Pack on
-its own. Not for when it's used inside of Rails.
-
== Download
The latest version of Action Pack can be found at
@@ -421,4 +406,4 @@ 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. \ No newline at end of file
+ new feature to be submitted in the form of new unit tests.