EmberCLI Rails: An Integration Love Story.
4 likes1,438 views
This document discusses integrating Ember.js frontend applications with Rails backends. It provides a brief introduction to Ember.js and its history alongside Rails. It then introduces the EmberCLI Rails gem, which aims to bridge EmberCLI and Rails by handling shared responsibilities like API testing generators and asset compilation/serving to provide a unified development experience. The goals of the gem are to avoid issues of complete separation between frontend and backend while maintaining their separation of concerns.
EmberCLI Rails: An Integration Love Story.
- 1. EmberCLI Rails An Integration Love Story
- 9. What I’ll be covering
- 10. • A brief intro to Ember.js • The History of Rails and Ember • Introduction to EmberCLI Rails gem • Goals of the EmberCLI Rails project
- 11. A Brief Intro to Ember.js
- 12. —Luke Melia “98% of building good apps is understanding your layers and knowing what code should go where.”
- 13. MVC
- 14. Well, Kinda.
- 15. More like MVCR+
- 16. Router • Application state • Updates URL per route transition
- 18. Views • DOM Interactions • DOM events to semantic actions
- 19. Controllers • Presenting data for view layer to render
- 20. Why Ember.js is appealing to Rails developers.
- 21. Yehuda
- 25. Focus on testing
- 26. Rails <3 Ember • Yehuda • Convention over configuration • Shared nomenclature* • Emphasis on meaningful URLs • Focus on Testing
- 28. The History of Rails and Ember
- 29. Globals and inline templates emberjs.jsbin.com
- 30. Ember Rails (gem) x Rails • Globals (still) • File Structure • Precompiled templates into asset pipeline API Testing Generators Asset Compilation Asset Serving
- 31. Ember AppKit • precursor to EmberCLI • Grunt build tooling • ES6 transpilation • Solid project structure • Frontend/backend package management via NPM/Bower
- 32. Bower
- 34. xx Ember AppKit Rails (gem) API Testing Generators Asset Compilation Asset Serving Rails Ember • Rails generators for AppKit resources • Tests accessible in Rails-land • Simple API versioning • Compiled to AMD
- 36. EmberCLI • Successor of Ember AppKit • Broccoli as a build tool • Testing harness out of the box • Constant improvements • Addons
- 37. Upgradability • Solid upgrade path with `ember init` • guided upgrade with blueprints used for diff
- 38. Complete Separation • Tested independently • Allows for greater specialization • Flexible backend • Separation of concerns at a system level xxAPI Testing Generators Asset Compilation Asset Serving Testing Rails Ember
- 39. No full-stack acceptance testing conventions
- 42. Doesn't work well with existing applications
- 45. The pitfalls of complete separation • No full-stack acceptance testing conventions • Ad hoc solutions to development workflow • Doesn't work with existing applications • Without excessive duplication • Deployments become more complicated (conventions)
- 46. The EmberCLI Rails gem Somewhere in Between...
- 47. Responsibilities of EmberCLI Rails xAPI Testing Rails x Generators Asset Compilation Asset Serving Testing Ember x x RA T Ge AssAs E
- 48. Responsibilities of EmberCLI Rails x x Rails API Testing Generators Asset Compilation Asset Serving Ember
- 49. How does it work?
- 51. How do I use it?
- 52. We start with a Rails app...
- 56. Goals of the EmberCLI Rails Project
- 58. Maybe we have some time for a demo? demo demo2 - shameless plug