Module: ActionView::Helpers::JavaScriptHelper

Defined in:
lib/action_view/helpers/javascript_helper.rb

Overview

Provides a set of helpers for calling JavaScript functions and, most importantly, to call remote methods using what has been labelled AJAX. This means that you can call actions in your controllers without reloading the page, but still update certain parts of it using injections into the DOM. The common use case is having a form that adds a new element to a list without reloading the page.

To be able to use the JavaScript helpers, you must either call <%= define_javascript_functions %> (which returns all the JavaScript support functions in a <script> block) or reference the JavaScript library using <%= javascript_include_tag "prototype" %> (which looks for the library in /javascripts/prototype.js). The latter is recommended as the browser can then cache the library instead of fetching all the functions anew on every request.

If you’re the visual type, there’s an AJAX movie demonstrating the use of form_remote_tag.

Constant Summary collapse

CALLBACKS =
[:uninitialized, :loading, :loaded, :interactive, :complete, :failure].push((100..599).to_a).flatten
AJAX_OPTIONS =
[ :before, :after, :condition, :url, :asynchronous, :method, 
:insertion, :position, :form, :with, :update, :script ].concat(CALLBACKS)
JAVASCRIPT_PATH =
File.join(File.dirname(__FILE__), 'javascripts')

Instance Method Summary collapse

Instance Method Details

#auto_complete_field(field_id, options = {}) ⇒ Object

Adds AJAX autocomplete functionality to the text input field with the DOM ID specified by field_id.

This function expects that the called action returns a HTML <ul> list, or nothing if no entries should be displayed for autocompletion.

You’ll probably want to turn the browser’s built-in autocompletion off, su be sure to include a autocomplete=“off” attribute with your text input field.

Required options are:

:url

Specifies the DOM ID of the element whose innerHTML should be updated with the autocomplete entries returned by XMLHttpRequest.

Addtional options are:

:update

Specifies the DOM ID of the element whose innerHTML should be updated with the autocomplete entries returned by the AJAX request. Defaults to field_id + ‘_auto_complete’

:with

A JavaScript expression specifying the parameters for the XMLHttpRequest. This defaults to ‘fieldname=value’.

:indicator

Specifies the DOM ID of an elment which will be displayed while autocomplete is running.



356
357
358
359
360
361
362
363
364
365
366
367
368
# File 'lib/action_view/helpers/javascript_helper.rb', line 356

def auto_complete_field(field_id, options = {})
  function =  "new Ajax.Autocompleter("
  function << "'#{field_id}', "
  function << "'" + (options[:update] || "#{field_id}_auto_complete") + "', "
  function << "'#{url_for(options[:url])}'"

  js_options = {}
  js_options[:callback]   = "function(element, value) { return #{options[:with]} }" if options[:with]
  js_options[:indicator]  = "'#{options[:indicator]}'" if options[:indicator]
  function << (', ' + options_for_javascript(js_options) + ')')

  javascript_tag(function)
end

#auto_complete_result(entries, field, phrase = nil) ⇒ Object

Use this method in your view to generate a return for the AJAX automplete requests.

Example action:

def auto_complete_for_item_title
  @items = Item.find(:all, 
    :conditions => [ 'LOWER(description) LIKE ?', 
    '%' + request.raw_post.downcase + '%' ])
  render :inline => '<%= auto_complete_result(@items, 'description') %>'
end

The auto_complete_result can of course also be called from a view belonging to the auto_complete action if you need to decorate it further.



383
384
385
386
387
# File 'lib/action_view/helpers/javascript_helper.rb', line 383

def auto_complete_result(entries, field, phrase = nil)
  return unless entries
  items = entries.map { |entry| ("li", phrase ? highlight(entry[field], phrase) : h(entry[field])) }
  ("ul", items)
end

#define_javascript_functionsObject

Includes the Action Pack JavaScript libraries inside a single <script> tag. The function first includes prototype.js and then its core extensions, (determined by filenames starting with “prototype”). Afterwards, any additional scripts will be included in random order.

Note: The recommended approach is to copy the contents of lib/action_view/helpers/javascripts/ into your application’s public/javascripts/ directory, and use javascript_include_tag to create remote <script> links.



272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
# File 'lib/action_view/helpers/javascript_helper.rb', line 272

def define_javascript_functions
  javascript = '<script type="text/javascript">'
  
  # load prototype.js and its extensions first 
  prototype_libs = Dir.glob(File.join(JAVASCRIPT_PATH, 'prototype*')).sort.reverse
  prototype_libs.each do |filename| 
    javascript << "\n" << IO.read(filename)
  end
  
  # load other librairies
  (Dir.glob(File.join(JAVASCRIPT_PATH, '*')) - prototype_libs).each do |filename| 
    javascript << "\n" << IO.read(filename)
  end
  javascript << '</script>'
end

#draggable_element(element_id, options = {}) ⇒ Object

Makes the element with the DOM ID specified by element_id draggable.

Example:

<%= draggable_element("my_image", :revert => true)

You can change the behaviour with various options, see script.aculo.us for more documentation.



464
465
466
# File 'lib/action_view/helpers/javascript_helper.rb', line 464

def draggable_element(element_id, options = {})
  javascript_tag("new Draggable('#{element_id}', #{options_for_javascript(options)})")
end

#drop_receiving_element(element_id, options = {}) ⇒ Object

Makes the element with the DOM ID specified by element_id receive dropped draggable elements (created by draggable_element). and make an AJAX call By default, the action called gets the DOM ID of the element as parameter.

Example:

<%= drop_receiving_element("my_cart", :url => { :controller => "cart", :action => "add" }) %>

You can change the behaviour with various options, see script.aculo.us for more documentation.



478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
# File 'lib/action_view/helpers/javascript_helper.rb', line 478

def drop_receiving_element(element_id, options = {})
  options[:with]     ||= "'id=' + encodeURIComponent(element.id)"
  options[:onDrop]   ||= "function(element){" + remote_function(options) + "}"
  options.delete_if { |key, value| AJAX_OPTIONS.include?(key) }
  
  if options[:accept] and options[:accept].kind_of?(Array)
    options[:accept] = "['#{options[:accept].join('\',\'')}']"
  elsif options[:accept]
    options[:accept] = "'#{options[:accept]}'" if options[:accept]
  end
  
  options[:hoverclass] = "'#{options[:hoverclass]}'" if options[:hoverclass]
  
  javascript_tag("Droppables.add('#{element_id}', #{options_for_javascript(options)})")
end

#escape_javascript(javascript) ⇒ Object

Escape carrier returns and single and double quotes for JavaScript segments.



495
496
497
# File 'lib/action_view/helpers/javascript_helper.rb', line 495

def escape_javascript(javascript)
  (javascript || '').gsub(/\r\n|\n|\r/, "\\n").gsub(/["']/) { |m| "\\#{m}" }
end

#evaluate_remote_responseObject

Returns ‘eval(request.responseText)’ which is the Javascript function that form_remote_tag can call in :complete to evaluate a multiple update return document using update_element_function calls.



231
232
233
# File 'lib/action_view/helpers/javascript_helper.rb', line 231

def evaluate_remote_response
  "eval(request.responseText)"
end

#form_remote_tag(options = {}) ⇒ Object

Returns a form tag that will submit using XMLHttpRequest in the background instead of the regular reloading POST arrangement. Even though it’s using JavaScript to serialize the form elements, the form submission will work just like a regular submission as viewed by the receiving side (all elements available in @params). The options for specifying the target with :url and defining callbacks is the same as link_to_remote.

A “fall-through” target for browsers that doesn’t do JavaScript can be specified with the :action/:method options on :html

form_remote_tag :html => { :action => url_for(:controller => "some", :action => "place") }

By default the fall-through action is the same as the one specified in the :url (and the default method is :post).



139
140
141
142
143
144
145
146
147
148
# File 'lib/action_view/helpers/javascript_helper.rb', line 139

def form_remote_tag(options = {})
  options[:form] = true

  options[:html] ||= {}
  options[:html][:onsubmit] = "#{remote_function(options)}; return false;"
  options[:html][:action] = options[:html][:action] || url_for(options[:url])
  options[:html][:method] = options[:html][:method] || "post"

  tag("form", options[:html], true)
end

#javascript_tag(content) ⇒ Object

Returns a JavaScript tag with the content inside. Example:

javascript_tag "alert('All is good')" # => <script type="text/javascript">alert('All is good')</script>


501
502
503
# File 'lib/action_view/helpers/javascript_helper.rb', line 501

def javascript_tag(content)
  ("script", content, :type => "text/javascript")
end

Returns a link that’ll trigger a javascript function using the onclick handler and return false after the fact.

Examples:

link_to_function "Greeting", "alert('Hello world!')"
link_to_function(image_tag("delete"), "if confirm('Really?'){ do_delete(); }")


32
33
34
35
36
37
# File 'lib/action_view/helpers/javascript_helper.rb', line 32

def link_to_function(name, function, html_options = {})
  (
    "a", name, 
    {:href => "#", :onclick => "#{function}; return false;"}.merge(html_options.symbolize_keys)
  )
end

Returns a link to a remote action defined by options[:url] (using the url_for format) that’s called in the background using XMLHttpRequest. The result of that request can then be inserted into a DOM object whose id can be specified with options[:update]. Usually, the result would be a partial prepared by the controller with either render_partial or render_partial_collection.

Examples:

link_to_remote "Delete this post", :update => "posts", :url => { :action => "destroy", :id => post.id }
link_to_remote(image_tag("refresh"), :update => "emails", :url => { :action => "list_emails" })

You can also specify a hash for options[:update] to allow for easy redirection of output to an other DOM element if a server-side error occurs:

Example:

link_to_remote "Delete this post",
    :url => { :action => "destroy", :id => post.id },
    :update => { :success => "posts", :failure => "error" }

Optionally, you can use the options[:position] parameter to influence how the target DOM element is updated. It must be one of :before, :top, :bottom, or :after.

By default, these remote requests are processed asynchronous during which various JavaScript callbacks can be triggered (for progress indicators and the likes). All callbacks get access to the request object, which holds the underlying XMLHttpRequest.

To access the server response, use request.responseText, to find out the HTTP status, use request.status.

Example:

link_to_remote word,
    :url => { :action => "undo", :n => word_counter },
    :complete => "undoRequestCompleted(request)"

The callbacks that may be specified are:

:loading

Called when the remote document is being loaded with data by the browser.

:loaded

Called when the browser has finished loading the remote document.

:interactive

Called when the user can interact with the remote document, even though it has not finished loading.

:complete

Called when the XMLHttpRequest is complete, and the HTTP status code is 200 OK.

:failure

Called when the XMLHttpRequest is complete, and the HTTP status code is anything other than 200 OK.

You can further refine :failure by adding additional callbacks for specific status codes:

Example:

link_to_remote word,
    :url => { :action => "action" },
    404 => "alert('Not found...? Wrong URL...?')",
    :failure => "alert('HTTP Error ' + request.status + '!')"

If you for some reason or another need synchronous processing (that’ll block the browser while the request is happening), you can specify options[:type] = :synchronous.

You can customize further browser side call logic by passing in JavaScript code snippets via some optional parameters. In their order of use these are:

:confirm

Adds confirmation dialog.

:condition

Perform remote request conditionally by this expression. Use this to describe browser-side conditions when request should not be initiated.

:before

Called before request is initiated.

:after

Called immediately after request was initiated and before :loading.



116
117
118
# File 'lib/action_view/helpers/javascript_helper.rb', line 116

def link_to_remote(name, options = {}, html_options = {})  
  link_to_function(name, remote_function(options), html_options)
end

#observe_field(field_id, options = {}) ⇒ Object

Observes the field with the DOM ID specified by field_id and makes an AJAX call when its contents have changed.

Required options are:

:url

url_for-style options for the action to call when the field has changed.

Additional options are:

:frequency

The frequency (in seconds) at which changes to this field will be detected. Set this to a value greater than zero to use time based observation instead of event based observation.

:update

Specifies the DOM ID of the element whose innerHTML should be updated with the XMLHttpRequest response text.

:with

A JavaScript expression specifying the parameters for the XMLHttpRequest. This defaults to ‘value’, which in the evaluated context refers to the new field value.

Additionally, you may specify any of the options documented in +link_to_remote.



310
311
312
313
314
315
316
# File 'lib/action_view/helpers/javascript_helper.rb', line 310

def observe_field(field_id, options = {})
  if options[:frequency]
    build_observer('Form.Element.Observer', field_id, options)
  else
    build_observer('Form.Element.EventObserver', field_id, options)
  end
end

#observe_form(form_id, options = {}) ⇒ Object

Like observe_field, but operates on an entire form identified by the DOM ID form_id. options are the same as observe_field, except the default value of the :with option evaluates to the serialized (request string) value of the form.



322
323
324
325
326
327
328
# File 'lib/action_view/helpers/javascript_helper.rb', line 322

def observe_form(form_id, options = {})
  if options[:frequency]
    build_observer('Form.Observer', form_id, options)
  else
    build_observer('Form.EventObserver', form_id, options)
  end
end

#periodically_call_remote(options = {}) ⇒ Object

Periodically calls the specified url (options[:url]) every options[:frequency] seconds (default is 10). Usually used to update a specified div (options[:update]) with the results of the remote call. The options for specifying the target with :url and defining callbacks is the same as link_to_remote.



123
124
125
126
127
# File 'lib/action_view/helpers/javascript_helper.rb', line 123

def periodically_call_remote(options = {})
   frequency = options[:frequency] || 10 # every ten seconds by default
   code = "new PeriodicalExecuter(function() {#{remote_function(options)}}, #{frequency})"
   ("script", code, options[:html_options] || {})
end

#remote_function(options) ⇒ Object

:nodoc: for now



235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
# File 'lib/action_view/helpers/javascript_helper.rb', line 235

def remote_function(options) #:nodoc: for now
  javascript_options = options_for_ajax(options)

  update = ''
  if options[:update] and options[:update].is_a?Hash
    update  = []
    update << "success:'#{options[:update][:success]}'" if options[:update][:success]
    update << "failure:'#{options[:update][:failure]}'" if options[:update][:failure]
    update  = '{' + update.join(',') + '}'
  elsif options[:update]
    update << "'#{options[:update]}'"
  end

  function = update.empty? ? 
    "new Ajax.Request(" :
    "new Ajax.Updater(#{update}, "

  function << "'#{url_for(options[:url])}'"
  function << ", #{javascript_options})"

  function = "#{options[:before]}; #{function}" if options[:before]
  function = "#{function}; #{options[:after]}"  if options[:after]
  function = "if (#{options[:condition]}) { #{function}; }" if options[:condition]
  function = "if (confirm('#{escape_javascript(options[:confirm])}')) { #{function}; }" if options[:confirm]

  return function
end

#sortable_element(element_id, options = {}) ⇒ Object

Makes the element with the DOM ID specified by element_id sortable by drag-and-drop and make an AJAX call whenever the sort order has changed. By default, the action called gets the serialized sortable element as parameters.

Example:

<%= sortable_element("my_list", :url => { :action => "order" }) %>

In the example, the action gets a “my_list” array parameter containing the values of the ids of elements the sortable consists of, in the current order.

You can change the behaviour with various options, see script.aculo.us for more documentation.



439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
# File 'lib/action_view/helpers/javascript_helper.rb', line 439

def sortable_element(element_id, options = {})
  options[:with]     ||= "Sortable.serialize('#{element_id}')"
  options[:onUpdate] ||= "function(){" + remote_function(options) + "}"
  options.delete_if { |key, value| AJAX_OPTIONS.include?(key) }
  
  [:tag, :overlap, :constraint].each do |option|
    options[option] = "'#{options[option]}'" if options[option]
  end
  
  if options[:containment] and options[:containment].kind_of?(Array)
    options[:containment] = "['#{options[:containment].join('\',\'')}']"
  elsif options[:containment]
    options[:containment] = "'#{options[:containment]}'" if options[:containment]
  end
  
  javascript_tag("Sortable.create('#{element_id}', #{options_for_javascript(options)})")
end

#submit_to_remote(name, value, options = {}) ⇒ Object

Returns a button input tag that will submit form using XMLHttpRequest in the background instead of regular reloading POST arrangement. options argument is the same as in form_remote_tag



152
153
154
155
156
157
158
159
160
161
162
# File 'lib/action_view/helpers/javascript_helper.rb', line 152

def submit_to_remote(name, value, options = {})
  options[:with] = 'Form.serialize(this.form)'

  options[:html] ||= {}
  options[:html][:type] = 'button'
  options[:html][:onclick] = "#{remote_function(options)}; return false;"
  options[:html][:name] = name
  options[:html][:value] = value

  tag("input", options[:html], false)
end

#text_field_with_auto_complete(object, method, tag_options = {}, completion_options = {}) ⇒ Object

Wrapper for text_field with added AJAX autocompletion functionality.

In your controller, you’ll need to define an action called auto_complete_for_object_method to respond the AJAX calls,

See the RDoc on ActionController::AutoComplete to learn more about this.



395
396
397
398
399
400
# File 'lib/action_view/helpers/javascript_helper.rb', line 395

def text_field_with_auto_complete(object, method, tag_options = {}, completion_options = {})
  (completion_options[:skip_style] ? "" : auto_complete_stylesheet) +
  text_field(object, method, { :autocomplete => "off" }.merge!(tag_options)) +
  ("div", "", :id => "#{object}_#{method}_auto_complete", :class => "auto_complete") +
  auto_complete_field("#{object}_#{method}", { :url => { :action => "auto_complete_for_#{object}_#{method}" } }.update(completion_options))
end

#update_element_function(element_id, options = {}, &block) ⇒ Object

Returns a Javascript function (or expression) that’ll update a DOM element according to the options passed.

  • :content: The content to use for updating. Can be left out if using block, see example.

  • :action: Valid options are :update (assumed by default), :empty, :remove

  • :position If the :action is :update, you can optionally specify one of the following positions: :before, :top, :bottom, :after.

Examples:

<%= javascript_tag(update_element_function(
      "products", :position => :bottom, :content => "<p>New product!</p>")) %>

<% replacement_function = update_element_function("products") do %>
  <p>Product 1</p>
  <p>Product 2</p>
<% end %>
<%= javascript_tag(replacement_function) %>

This method can also be used in combination with remote method call where the result is evaluated afterwards to cause multiple updates on a page. Example:

# Calling view
<%= form_remote_tag :url => { :action => "buy" }, :complete => evaluate_remote_response %>
all the inputs here...

# Controller action
def buy
  @product = Product.find(1)
end

# Returning view
<%= update_element_function(
      "cart", :action => :update, :position => :bottom, 
      :content => "<p>New Product: #{@product.name}</p>")) %>
<% update_element_function("status", :binding => binding) do %>
  You've bought a new product!
<% end %>

Notice how the second call doesn’t need to be in an ERb output block since it uses a block and passes in the binding to render directly. This trick will however only work in ERb (not Builder or other template forms).



202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
# File 'lib/action_view/helpers/javascript_helper.rb', line 202

def update_element_function(element_id, options = {}, &block)
  
  content = escape_javascript(options[:content] || '')
  content = escape_javascript(capture(&block)) if block
  
  javascript_function = case (options[:action] || :update)
    when :update
      if options[:position]
        "new Insertion.#{options[:position].to_s.camelize}('#{element_id}','#{content}')"
      else
        "$('#{element_id}').innerHTML = '#{content}'"
      end
    
    when :empty
      "$('#{element_id}').innerHTML = ''"
    
    when :remove
      "Element.remove('#{element_id}')"
    
    else
      raise ArgumentError, "Invalid action, choose one of :update, :remove, :empty"
  end
  
  javascript_function << ";\n"
  options[:binding] ? concat(javascript_function, options[:binding]) : javascript_function
end

#visual_effect(name, element_id = false, js_options = {}) ⇒ Object

Returns a JavaScript snippet to be used on the AJAX callbacks for starting visual effects.

Example:

<%= link_to_remote "Reload", :update => "posts", 
      :url => { :action => "reload" }, 
      :complete => visual_effect(:highlight, "posts", :duration => 0.5 )

If no element_id is given, it assumes “element” which should be a local variable in the generated JavaScript execution context. This can be used for example with drop_receiving_element:

<%= drop_receving_element (...), :loading => visual_effect(:fade) %>

This would fade the element that was dropped on the drop receiving element.

You can change the behaviour with various options, see script.aculo.us for more documentation.



420
421
422
423
# File 'lib/action_view/helpers/javascript_helper.rb', line 420

def visual_effect(name, element_id = false, js_options = {})
  element = element_id ? "'#{element_id}'" : "element"
  "new Effect.#{name.to_s.capitalize}(#{element},#{options_for_javascript(js_options)});"
end