Say I need to call a javascript file in the <head> of an ERb template.
My instinct is to do the usual:
<head>
<%= javascript_include_tag :defaults %> <!-- For example -->
</head>
in my application's layout. The problem of course becoming that these javascript files are loaded into every page in my application, regardless of whether or not they are needed for the page being viewed.
So what I'm wondering is if there's a good way of loading a javascript into the the headers of, for example, all ERb templates found only in a specific directory.
I would use content_for.
For instance, specify the place to insert it in the application layout:
<head>
<title>Merry Christmas!</title>
<%= yield(:head) -%>
</head>
And send it there from a view:
<%- content_for(:head) do -%>
<%= javascript_include_tag :defaults -%>
<%- end -%>
I feel there's nothing wrong including all yr defaults since they can then be cached on user's browser.
I would suggest not to add javascript in the header as it causes to load the page slower. Rather load the js at the bottom of the page, which is faster. http://developer.yahoo.com/performance/rules.html#js_bottom
<body>
....
<%= yield(:js) -%>
</body>
And send it there from a view:
<%- content_for(:js) do -%>
<%= javascript_include_tag :defaults -%>
<%- end -%>
I usually have the following in the layout file:
<head>
<%= javascript_include_tag :defaults %> <!-- For example -->
<%= @extra_head_content %>
</head>
And then in the views:
<% (@extra_head_content ||= "") += capture do %>
<%= other_content %>
<% end %>
See the API documentation for #capture
来源：https://stackoverflow.com/questions/390164/javascript-include-tag-best-practice-in-a-rails-application