Rails Concerns and Turbolinks
Download as PPTX, PDF0 likes503 views
Concerns provide a way to keep code organized and DRY by extracting common code chunks. They allow cleaning up fat models/controllers. Concerns are supported in Rails 3 but became more official in Rails 4 with concerns directories. Concerns DRY model codes and skin-nize fat models. Controller concerns also allow DRYing. Turbolinks prevents full page reloads between changes by using JavaScript pushState like PJAX but loads the full page instead of parts. Turbolinks improves page loads when pages share assets but PJAX is better for server performance.
Rails Concerns and Turbolinks
- 1. Rails Concerns and Turbolinks Presented by Zahidul Hasan
- 2. What is Concerns? • Concerns provides a way that allow us to keep our code organized and DRY • Basically, the idea is to extract common and/or context specific chunks of code in order to clean up the models/controllers and avoid them from getting too fat and messy
- 3. More Information • Concerns are supported by Rails 3 but have become more official in Rails 4 • Those who have worked with a Rails 4 app, might have probably noticed the app/models/concerns and app/controllers/concerns directories
- 4. Why should we use concerns? • DRYing up model codes • Skin-nizing Fat Models
- 5. DRYing up model codes
- 6. Create a commentable.rb file in app/model/concerns
- 8. • Create a attendable.rb file in app/model/concern/event folder
- 9. • Create a commentable.rb file in app/model/concern/event folder
- 11. Controller Concerns • Controllers can also have concerns • Purpose will be the same: DRYing
- 12. Turbolinks • Feature of rails 4 • Prevents the browser from reloading the JavaScript and CSS between each page change • Its almost similar to PJAX
- 13. JavaScript pushState • Javascript API for HTML5: History Interface • pushState can be used to store the navigation history
- 14. PJAX • PJAX is a combination of the terms pushState and AJAX • Instead of reloading the whole page when clicking a link, just load the part of the page that needs updating • On the client-side we have to define the container that should be replaced when a link is clicked
- 15. Turbolinks • Instead of replacing only parts a page it loads a complete website from the server and replaces the <title> and <body> in the currently loaded DOM • Unlike PJAX we don't have to mark links and containers, Turbolinks will handle that for us
- 16. Comparison between Turbolinks and PJAX • Turbolinks definitely improve client-side page loading, but the server still has to render the complete website • PJAX renders only those parts of a website that really need to be updated, need additional work when developing the application • Turbolinks will improve page load significantly if the pages share JavaScript and CSS styling. PJAX comes in handy, when server-side performance is an issue
- 17. Thank You