Rails 3.1
Download as KEY, PDFā¢0 likesā¢1,210 views
The document discusses the significant updates in Rails 3.1, including changes to jQuery, CoffeeScript, and Sass, along with the asset pipeline implementation. It highlights optional features and migration strategies for developers, noting that Rails 3.2 has fewer changes. Additionally, it covers practical tips for upgrading applications and addresses common problems encountered during development.
Rails 3.1
- 1. Rails 3.1 Lori Olson Confoo 2012 Montreal, QC
- 2. Another new version of Rails. Delightful. And terrifying. What's changed this time?
- 3. Summary ā¢ jQuery ā¢ CoffeeScript ā¢ SASS ā¢ Asset Pipeline ā¢ Miscellaneous cool stuff
- 4. But... ā¢ What about Rails 3.2? ā¢ only released a few weeks ago ā¢ not nearly as many scary changes
- 5. jQuery
- 6. What you HAVE to know ā¢ How to go back to Prototype (not recommended ā¢ rails new my_app -j prototype
- 7. Differences ā¢ Gemļ¬le gem ājquery-railsā ā¢ application.js //= require jquery //= require jquery_ujs
- 10. CoffeeScript
- 11. What you HAVE to know ā¢ Nothing ā¢ Absolutely not required ā¢ Just remove one line from Gemļ¬le ā¢ gem 'coffee-rails' ā¢ And you donāt even have to do this
- 12. Thomas Fuchs on CoffeeScript ā¢ May 2011 - "I just like javascript too much to have a use for that, but I understand why other people might like it" ā¢ Aug 2011 - There, it happened. Mistakenly typed CoffeeScript in a .js ļ¬le. So easy to pick up, and so natural.
- 13. CoffeeScript Resources ā¢ Railscasts ā¢ CoffeeScript Basics ā¢ http://railscasts.com/episodes/267-coffeescript-basics ā¢ Peepcode ā¢ Meet CoffeeScript ā¢ http://peepcode.com/products/coffeescript ā¢ Books ā¢ Pragmatic Programmers - CoffeeScript ā¢ OāReilly - The Little Book on CoffeeScript
- 14. SASS
- 15. What you HAVE to know ā¢ Nothing ā¢ Absolutely not required ā¢ Just remove one line from your Gemļ¬le ā¢ gem 'sass-rails' ā¢ And you donāt even have to do that
- 16. Is it SASS or SCSS? ā¢ Sass is the older style HAML-like indented syntax ā¢ SCSS is the new main syntax, which is a superset of CSS3
- 17. Why SASS? ā¢ Variables ā¢ Nesting ā¢ DRY up your styles ā¢ Mixins ā¢ reusable chunks ā¢ with arguments! ā¢ Selector Inheritance
- 18. Alternatives to SASS ā¢ Less ā¢ HSS ā¢ Other, technology speciļ¬c ā¢ XCSS (PHP) ā¢ CleverCss (Python) ā¢ CSS Crush (PHP)
- 19. Asset Pipeline
- 20. assets dir
- 21. assets dir
- 22. assets dir
- 23. assets dir
- 24. js manifest ā¢ Powered by - Sprockets ā¢ application.js // FIXME: Tell people that this is a manifest ļ¬le, real code should go into discrete ļ¬les // //= require jquery //= require jquery_ujs //= require_tree .
- 25. SASS - no sprockets ā¢ probably donāt want to use manifests ā¢ use @import, or your variables and scopes will not work
- 26. Dev vs Production ā¢ To precompile, or not to precompile ā¢ Heroku ā¢ Cedar stack ā¢ counter-intuitive settings
- 27. Compression ā¢ Ugliļ¬er (for javascript) ā¢ SCSS (for css)
- 28. But, Why?
- 29. Identity Map
- 30. enabling ā¢ application.rb # Enable IdentityMap for Active Record, to disable set to false or remove the line below. conļ¬g.active_record.identity_map = true
- 31. problems ā¢ associations ā¢ STI ā¢ tests
- 33. class Project < ActiveRecord::Base has_many :tasks has_many :assignments, :through => :tasks has_many :users, :through => :assignments end
- 34. Migrations
- 35. class CreateProjects < ActiveRecord::Migration def change create_table :projects do |t| t.string :name t.timestamps end end end
- 36. HTTP Streaming
- 37. requirements ā¢ Ruby 1.9.2 (min) ā¢ Web server support ā¢ nginx ā¢ unicorn
- 38. Examples
- 39. New App
- 40. Upgrade
- 41. Bundler ā¢ Did you know... you can use bundler all the way down to Rails 2.1 apps?
- 43. ā¢ Upgrade the Gemļ¬le ā¢ Conļ¬g ļ¬le changes ā¢ Move the assets
- 44. Configs ā¢ boot.rb ā¢ conļ¬g.rb ā¢ development.rb ā¢ production.rb
- 45. Assets ā¢ Move asset folders ā¢ Fix image references ā¢ Manifests ā¢ stylesheet and javascript tag references
- 46. Upgrade Demo ā¢ Upgrading a Rails 2.1 app to Rails 3.1 in 1ā¦
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: So, out with the old, and in with the new. Prototype was the default Javascript library in Rails since the very beginning. There have been rumblings for several (intermediate) versions, but they finally pulled the trigger and did it.\n
- #7: However, if you just HAVE to use Prototype, it is just a simple -j option away. The choice of Javascript libs is now tucked away into a couple of gems\n\n\n
- #8: gem 'jquery-rails' or gem 'prototype-rails' will show up in your Gemfile\nAnd prototype or jquery js will be included via your application javascript manifest file\n- But, I get ahead of myself\n\n
- #9: Almost 10x more popular than Prototype\n\nPopularity == ecosystem\n\nVersioning... rails dictates which jQuery version now, which is better\n
- #10: Infographic\nfile:///Volumes/loriolson/Confoo/Javascript%20Frameworks%20and%20jQuery%20(Infographic)%20%7C%20Web%20Resources%20%7C%20WebAppers.webarchive\n
- #11: \n
- #12: But it&#x2019;s important to note that CoffeeScript, while defined as a dependency by default in Rails 3.1, is not a requirement. You can just stick with pure Javascript (and jQuery) and call it done.\n\nNow, I consider myself just a dabbler in CoffeeScript, so I won&#x2019;t spend a lot of time on it.\n\n
- #13: Thomas Fuchs, author of the Scriptaculous framework, co-author of the JavaScript Performance Rocks! ebook had this to say about CoffeeScript\n
- #14: However, if you really want to learn it, and I suggest you do, there are some great resources out there. \n
- #15: Syntactically Awesome Stylesheets\n
- #16: \n
- #17: Guess which one is recommended? ;-)\n
- #18: \n
- #19: \n
- #20: It makes CSS and JavaScript first-class code citizens and enables proper organization, including use in plugins and engines\n
- #21: So, the assets (images, javascripts, & stylesheets) have been tucked under public, all this time.\n\nNow, they are slotted in under the app/assets directory\n
- #22: So, the assets (images, javascripts, & stylesheets) have been tucked under public, all this time.\n\nNow, they are slotted in under the app/assets directory\n
- #23: So, the assets (images, javascripts, & stylesheets) have been tucked under public, all this time.\n\nNow, they are slotted in under the app/assets directory\n
- #24: So, the assets (images, javascripts, & stylesheets) have been tucked under public, all this time.\n\nNow, they are slotted in under the app/assets directory\n
- #25: \n
- #26: \n
- #27: generate something to run on heroku to demo diff\n
- #28: \n
- #29: Average load time\nNumber of resource requests\nCDN\n\n
- #30: Active Record has an Identity Map in Rails 3.1. An identity map keeps previously instantiated records and returns the object associated with the record if accessed again. The identity map is created on a per-request basis and is flushed at request completion.\nRails 3.1 comes with the identity map turned off by default. There are issues...\n
- #31: \n
- #32: \n
- #33: \n
- #34: Didn&#x2019;t used to be able to nest these\n\nWord of warning. You may, or may not run into problems on non-default databases. And I can practically guarantee the you will have problems if you used this in conjunction with a legacy database with composite primary keys.\n
- #35: change\n
- #36: Instead of up and down. This works for straight-forward migrations, but if you are doing something special, you will probably still want up & down.\n
- #37: HTTP Streaming is another change that is new in Rails 3.1. This lets the browser download your stylesheets and JavaScript files while the server is still generating the response. This requires Ruby 1.9.2, is opt-in and requires support from the web server as well, but the popular combo of nginx and unicorn is ready to take advantage of it.\n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n