search

danmaclean / gee_fu

An extensible Ruby on Rails web-service application and database for visualising HTGS data
18 stars 5 forks source link

jQuery Autocomplete #42

Closed mrship closed 11 years ago

mrship commented 11 years ago

@danmaclean Can you remind me where you were using jQuery autocomplete? I need to test that is still working...

danmaclean commented 11 years ago

in the web forms when asking for a chromosome to look for features on. So features/index.html.erb with code like this

<% @genomes.each do |g| %> <%= "<input id=\"genome_id_#{g.id}\" name=\"genome_id\" type=\"radio\" value=\"#{g.id}\" class=\"genome_button\" onMouseUp=get_chromosomes(\"#{g.id}\") />".html_safe %> <%= label_tag(:genome_id, "#{g.build_version}") %> <% end %><br/>

The js function being get_chromosome()

mrship commented 11 years ago

Looking at this code, I don't see what the site feature actually is though. Even if I run it on the old code under Rails 2 nothing happens in the UI when I click on a genome. It calls out to the server, but is getting a cached response (a 304 HTTP return) so I don't see how this ever worked?

Can you advise on what this should actually do?

danmaclean commented 11 years ago

When trying to use the webforms to find features, the user would have to choose the genome version the features are on. The user would select a genome build then the autocomplete would take that info and look up all the references in that genome so that typing the name of the reference you would want would be autocompletes. The route was /genomes/reference_list/' + genome_id + '.json' and I seem to remember that it required the genome build to be clicked and mouseUp to happen before it went and got the genomes references. It was working the last time I tried it, on the Ruby 1.8 version of this. I can't imagine the fixed routes have messed this up so Im not sure what is going wrong.

mrship commented 11 years ago

OK, I've got this working see #45.