Ruby formµÄÁ½ÖÖд·¨

ÏÂÃæ½éÉÜRuby formµÄÁ½ÖÖд·¨¡£
Ruby formд·¨Ò»£ºÊ¹ÓÃform_for
< % form_for :order, :url => { :action => :save_order } do |form| %>   < p>    < %= label :order, :name, "Name:" %>    < %= form.text_field :name, :size => 40 %>     < /p>   < p>    < %= label :order, :address, "Address:" %>    < %= form.text_area :address, :rows => 3, :cols => 40 %>   < /p>   < p>    < %= label :order, :email, "E-Mail:" %>    < %= form.text_field :email, :size => 40 %>   < /p>   < %= submit_tag "Place Order" , :class => "submit" %> < % end %> 
À´¿´¿´½âÊÍ
ÒýÓÃ
There are two interesting things in this code. First, the form_for helper on line 1 sets up a standard HTML form. But it does more. The first parameter, : order,tells the method that it’s dealing with an object in an instance variable named @order. The helper uses this information when naming fields and when arranging for the field values to be passed back to the controller.
The :url parameter tells the helper what to do when the user hits the submit button. In this case, we’ll generate an HTTP POST request that’ll end up getting handled by the save_order action in the controller.
¶øÿ¸öformµÄhelper·½·¨£¬Èçform.text_area,form_text_field,ºóÃæ¸úµÄ·ûºÅ£¬Èç:name,:address,:email£¬µÈ¶¼ÊÇÕâ¸ömodelµÄÊôÐÔ¡£form_f