aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt
diff options
context:
space:
mode:
authorMike Gunderloy <MikeG1@larkfarm.com>2008-10-16 10:40:58 -0500
committerMike Gunderloy <MikeG1@larkfarm.com>2008-10-16 10:40:58 -0500
commit5c90c988f81b3ca3bfe74ce413c882ce9f17d501 (patch)
tree2235eb57b848bdb2aa4121ec38e4baffe9009cb8 /railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt
parentecfcb498d09dd4c618776c10a07977fd3b8dd4f0 (diff)
downloadrails-5c90c988f81b3ca3bfe74ce413c882ce9f17d501.tar.gz
rails-5c90c988f81b3ca3bfe74ce413c882ce9f17d501.tar.bz2
rails-5c90c988f81b3ca3bfe74ce413c882ce9f17d501.zip
A few updates to Getting Started guide
Diffstat (limited to 'railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt')
-rw-r--r--railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt b/railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt
index 0098f1d225..b6d8203c8b 100644
--- a/railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt
+++ b/railties/doc/guides/getting_started_with_rails/getting_started_with_rails.txt
@@ -18,6 +18,7 @@ This guide is designed for beginners who want to get started with a Rails applic
It is highly recommended that you *familiarize yourself with Ruby before diving into Rails*. You will find it much easier to follow what's going on with a Rails application if you understand basic Ruby syntax. Rails isn't going to magically revolutionize the way you write web applications if you have no experience with the language it uses. There are some good free resources on the net for learning Ruby, including:
+* link:http://www.humblelittlerubybook.com/[Mr. Neigborly’s Humble Little Ruby Book]
* link:http://www.rubycentral.com/book/[Programming Ruby]
* link:http://poignantguide.net/ruby/[Why's (Poignant) Guide to Ruby]
@@ -510,7 +511,7 @@ This view iterates over the contents of the +@posts+ array to display content an
* +link_to+ builds a hyperlink to a particular destination
* +edit_post_path+ is a helper that Rails provides as part of RESTful routing. You’ll see a variety of these helpers for the different actions that the controller includes.
-TIP: For more details on the rendering process, see link:../actionview/layouts_and_rendering [Layouts and Rendering in Rails].
+TIP: For more details on the rendering process, see link:../actionview/layouts_and_rendering.html[Layouts and Rendering in Rails].
=== Customizing the Layout
@@ -584,7 +585,9 @@ The +new.html.erb+ view displays this empty Post to the user:
<%= link_to 'Back', posts_path %>
-------------------------------------------------------
-The +form_for+ block is used to create an HTML form. Within this block, you have access to methods to build various controls on the form. For example, +f.text_field :name+ tells Rails to create a text input on the form, and to hook it up to the +name+ attribute of the instance being displayed. Rails uses +form_for+ in preference to having your write raw HTML because the code is more succinct, and because it explicitly ties the form to a particular model instance.
+The +form_for+ block is used to create an HTML form. Within this block, you have access to methods to build various controls on the form. For example, +f.text_field :name+ tells Rails to create a text input on the form, and to hook it up to the +name+ attribute of the instance being displayed. You can only use these methods with attributes of the model that the form is based on (in this case +name+, +title+, and +content+). Rails uses +form_for+ in preference to having your write raw HTML because the code is more succinct, and because it explicitly ties the form to a particular model instance.
+
+TIP: If you need to create an HTML form that displays arbitrary fields, not tied to a model, you should use the +form_tag+ method, which provides shortcuts for building forms that are not necessarily tied to a model instance.
When the user clicks the +Create+ button on this form, the browser will send information back to the +create+ method of the controller (Rails knows to call the +create+ method because the form is sent with an HTTP POST request; that's one of the conventions that I mentioned earlier):