Consuming ID returned by JQuery Autocomplete

This autocompete definition in Participants controller:

autocomplete :participant, :full_name, :display_value => :full_name, :full => true

and this pair of Rails tags:

<%= f.autocomplete_field :name,  
     autocomplete_participant_name_students_path, 
     :id_element => '#participantt_id' %>
  
<%= hidden_field :participant, :id %>

resulting in this HTML

<input data-autocomplete="/participant/autocomplete_participant_full_name"      
  id="full_name" 
  id_element="#participant_id"
  name="full_name" type="text" value="" />  
<input id="participant_id" name="participant[id]" type="hidden" />

does the trick for delivering ID of object found from autocomplete into hidden input field. The value is, then, of course, available as a request parameter when enclosing form is submitted. Your controller accesses this param as such:

Participant.find(params[:participant][:id])


I have tested this in both 0.6.1 and 1.0.4 versions of rails3-jquery-autocomplete gem, using Rails 3.1.1.

Gem Versioning

Within Gemfile you can constrain which version or versions of a gem your application is dependent upon.

Any gem inclusion without a version number indicates 'latest' version of gem should be used.

Specifying a gem as such:

gen 'foo', '=3.0'

indicates a specific version must be used.

Specifying a gem as such

gem 'foo', '>= 3.0'

indicates a version >= 3.0 is suitable. In general, you get what you expect from

= Equals version
!= Not equal to version
> Greater than version
< Less than version
>= Greater than or equal to
<= Less than or equal to

Gem versions can also be specified with the 'approximately greater than' operator. This operator increment final digit of a version up until next significant digit would turn over. So, a gem specification of

gem 'foo', '~> 3.1'

is satisfied with any version from 3.1 up to 3.9. inclusive. If three digits are specified in a version number used with ~> operator, as below

gem 'foo', '~> 3.1.1'

then the gem versions compatible with the application are 3.1.1 through 3.1.9, inclusive.

Autocomplete Details

https://github.com/crowdint/rails3-jquery-autocomplete

Rails: Calling Controller Action using onclick and Ajax (remote_function)

Say you want to call the update_reasons action in the reports controller in response to an onclick on a checkbox.

First, of course, you need the route in config/routes.rb



match "/reports/update_reasons" => "reports#update_reasons"



And, of course, the action...I just echo relevant arguments in this version.

Note, I render "nothing" because operation does not result in any view change beyond status change of checkbox which is managed by browser.

def update_reasons
  checked = params[:checked]
  params.each do |key, value|
    if /reasons_(\d+)/.match(value) != nil
      logger.debug("update reason #{$1} to #{checked}")
    end
  end
  respond_to do |format|
    format.js { render  :nothing => true }
  end
end

Using the check_box_tag, you will include on :onclick parameter. The value of :onclick is javascript. The "best" way to generate that javascript is using remote_function helper. I use the :with parameter to send request parameters

with the Ajax call. Notice in ruby code above reference to parameter names appearing in value of :with string in view code.



Here is my view code:

<% reasons.each do |infraction| %>
    <% rf =  remote_function(
       :url => { :controller => 'reports', 
               :action => :update_reasons },
       :with => '\'reason=\'+ this.id + \'&checked=\' + this.checked')  %>
    <%= check_box_tag "reasons[#{infraction.id}]", 
      infraction.description,
      false ,
      :onclick => "#{rf}",
      :class=>:"iToggle", :title=>"YES|NO" %>
    <%= infraction.description %>  
  <% end %>

If I expect some server-side generated change to view, I could include an :update argument to remote_function. This parameter names a div into rendered output is placed.

I admit I took a lazy approach by placing value of remote_function to a local variable. After much hair-pulling,I gave on trying to get quotes right with remote_function as direct value of :onclick parameter.

Contact Reasons Associated with a Report

I have added a method to RelationshipToReport model that returns a list of only those 'relationships' that apply to a given report type. The method name is for.

Here is an example usage:

infractions = RelationshipToReport.for(report)
infractions.each do |infraction|
...
end


Javascript and Rails

I have learned two things in the last 24 hours:

Javascript in partials

You can't place <% javascript_tag do %> in partials if you expect your javascript to be seen.

Multiple Requests as a Result of Form Submit

Multiple inclusions of js files, e.g. rails.js can cause multiple events/requests to be posted as a result of form submit. This is very hard to debug, but rails server shows, e.g. multiple GET requests being performed.

Cucumber on Windows

You must augment instructions from RSpec book for installing Cucumber on Windows. Specifically, you need to download MinGW for gcc (c compiler) and make. MinGW is
available from http://www.mingw.org/

When installing MinGW, make sure you select MSYS Developer Kit when stepping through installer.

To access gcc, you need to augment PATH environment variable to include C:\MinGW\bin.
To access make, you need to include C:\MinGW\msys\1.0\bin on your PATH environment variable. See Control Panel->System->Advanced->Environment Variables to edit PATH environment variable.