jangosteve / rails-jquery-demo

Demo Rails App with jQuery UJS

Demo Rails 3.1 App with jQuery UJS (AJAX)

This is a very simple demo Rails 3.1 with all CRUD (create, read, update, delete) functionality in AJAX using the jquery-rails gem which bundles jquery-ujs.

For relevant code, see the Comments controller and views. Also see unobtrusive bindings in app/assets/javascripts/comments.js.

Documentation & Resources

Documentation and resources for the Rails jquery-ujs may be found in the following articles:

• Rails 3 Remote Links and Forms: A Definitive Guide
• Rails 3 Remote Links and Forms Part 2: Data-type with jQuery
• http://www.alfajango.com/blog/rails-jquery-ujs-now-interactive/
• New ajax:aborted Rails jQuery UJS Hooks
• Wiki

Also, see the remotipart branch for AJAX file-upload functionality.

rails-jquery-demo's Issues

report_activate_error': Could not find RubyGem railties (>= 0) (Gem::LoadError)

I'm getting this error after I do a bundle install. Is there a live demo I could check out? That's all I'm after really. No need to check it out locally to evaluate.

Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/actionmailer-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x000001060cdc60 3.2.0"]
Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/actionpack-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x00000105139358 3.2.0"]
Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/activemodel-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x000001060544f0 3.2.0"]
Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/activerecord-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x00000102fe5760 3.2.0"]
Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/activeresource-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x0000010583be58 3.2.0"]
Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/rails-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x000001016f0e58 3.2.0"]
Invalid gemspec in [/Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/specifications/railties-3.2.0.gemspec]: Illformed requirement ["#Syck::DefaultKey:0x00000104b1cad8 3.2.0"]
/Users/adam/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:861:in report_activate_error': Could not find RubyGem railties (>= 0) (Gem::LoadError) from /Users/adam/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:255:inactivate'
from /Users/adam/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:1204:in gem' from /Users/adam/.rvm/gems/ruby-1.9.2-p136@jangosteve-rails/bin/rails:18:in

'

remotipart tests fails

are the specs in the remotipart branch supposed to run through? Because they don't when I test it.

Came to it because of JangoSteve/remotipart#39 - the ajax:success callback doesn't trigger for me when submitting files. It does trigger when the form does not contain files.

fix remotipart specs for chrome

Hi, when I change the driver to chrome, two specs fail. In the spec_helper:

Capybara.register_driver :selenium_chrome do |app|
  Capybara::Selenium::Driver.new(app, :browser => :chrome)
end
Capybara.javascript_driver = :selenium_chrome

results in

Failed examples:

rspec ./spec/features/comments_spec.rb:323 # comments only submits via remotipart when a file upload is present
rspec ./spec/features/comments_spec.rb:359 # comments Disables submit button while submitting with remotipart

Using OS X 10.8 and Chrome 28.

Why not test for current page instead of the "page_should_not_redirect" method

Just out of curiosity. You wrote this funky method to see if the browser redirects or not after clicking a link here, but I was just wondering why you don't just test for the current page after the click, like so:

click_button 'Create Comment'
current_path.should eq( root_path )

instead of

page_should_not_redirect do
  click_button 'Create Comment'
end