Using Rails without Rails

Transcript

1. Slide intentionally left blank Tuesday, April 24, 12
2. Using Rails without Rails Tuesday, April 24, 12
3. Using Rails without Rails Tuesday, April 24, 12
4. Piotr Sarnacki Tuesday, April 24, 12
5. @drogus Tuesday, April 24, 12
6. Poland Tuesday, April 24, 12
7. mixbook.com Tuesday, April 24, 12
8. Fair warning Tuesday, April 24, 12
9. Fair warning ! Tuesday, April 24, 12
10. Production use? Tuesday, April 24, 12
11. Production use? who cares? Tuesday, April 24, 12
12. Why? Tuesday, April 24, 12
13. Experimentation. Tuesday, April 24, 12
14. Experimentation. Inspiration. Tuesday, April 24, 12
15. Experimentation. Inspiration. Fun. Tuesday, April 24, 12
16. I could find some arguments Tuesday, April 24, 12
17. I could find some arguments using code as a documentation Tuesday, April 24, 12
18. I could find some arguments using code as a documentation fixing bugs by yourself Tuesday, April 24, 12
19. I could find some arguments using code as a documentation fixing bugs by yourself solutions for non-standard problems Tuesday, April 24, 12
20. But ultimately Tuesday, April 24, 12
21. But ultimately It’s for FUN Tuesday, April 24, 12
22. Texas Tuesday, April 24, 12
23. Tuesday, April 24, 12
24. Rails Tuesday, April 24, 12
25. Big Rails Tuesday, April 24, 12
26. Big Rails Many parts Tuesday, April 24, 12
27. Big Rails Many parts Complicated Tuesday, April 24, 12
28. Rails (>=3.0) Tuesday, April 24, 12
29. Modular Rails (>=3.0) Tuesday, April 24, 12
30. Learn! Tuesday, April 24, 12
31. But how to make it easier? Learn! Tuesday, April 24, 12
32. But how to make it easier? Learn! Minimal working version. Tuesday, April 24, 12
33. Start with something small and extend to know what are the possibilities. Tuesday, April 24, 12
34. Start with something small and extend to know what are the possibilities. Tuesday, April 24, 12
35. Start with something small and extend to know what are the possibilities. Tuesday, April 24, 12
36. Give me teh codez Tuesday, April 24, 12
37. A lot of codez Tuesday, April 24, 12
38. Problem Tuesday, April 24, 12
39. I want to check how does Action Controller work Problem Tuesday, April 24, 12
40. module ActionController class Base < Metal include Helpers include Cookies include HideActions include Streaming # around 25 more includes end end Simplified ActionController implementation Tuesday, April 24, 12
41. module ActionController class Metal < AbstractController::Base def params def content_type def status def self.dispatch # basically HTTP stuff end end What’s that ActionController::Metal? Tuesday, April 24, 12
42. require 'abstract_controller' class MyController < AbstractController::Base def index "foo" end end MyController.new.process(:index) #=> "foo" Abstract Controller Tuesday, April 24, 12
43. require 'abstract_controller' class MyController < AbstractController::Base include AbstractController::Rendering append_view_path "." def index render end end MyController.new.process(:index) # will try to render my/index Abstract Controller Tuesday, April 24, 12
44. module Foo def render print "foo " super end end class Base def render print "base" end end class MyBase < Base include Foo end MyBase.new.render # foo base Tuesday, April 24, 12
45. require 'abstract_controller' class MyController < AbstractController::Base include AbstractController::Rendering include AbstractController::Layouts append_view_path "." layout "application" def index render end end MyController.new.process(:index) # will try to render my/index with # with "application" layout Tuesday, April 24, 12
46. require 'abstract_controller' class MyController < AbstractController::Base include AbstractController::Rendering include AbstractController::Layouts include AbstractController::Helpers append_view_path "." layout "application" def index render :inline => "<%= foo %>" end private def foo "foo helper" end helper_method :foo end MyController.new.process(:index) # foo helper Tuesday, April 24, 12
47. For more, look at the code! gist.github.com/2482523 You can start here: Tuesday, April 24, 12
48. Good design Tuesday, April 24, 12
49. Reusable Good design Tuesday, April 24, 12
50. Reusable Good design Decoupled Tuesday, April 24, 12
51. A lot of APIs in Rails is just synctactic sugar over other APIs Tuesday, April 24, 12
52. Design is about pulling things apart Rich Hickey Tuesday, April 24, 12
53. Problem Tuesday, April 24, 12
54. I want to check how does Action View work Problem Tuesday, April 24, 12
55. ActionView::Base? Tuesday, April 24, 12
56. ActionView::Base? A lot of things there Tuesday, April 24, 12
57. Where to start? Tuesday, April 24, 12
58. AbstractController::Rendering Tuesday, April 24, 12
59. Ingredients Tuesday, April 24, 12
60. ActionView::LookupContext Tuesday, April 24, 12
61. ActionView::LookupContext Responsible for templates lookup. Tuesday, April 24, 12
62. ActionView::LookupContext paths = ActionView::PathSet.new(["views"]) lookup_context = ActionView::LookupContext.new( paths, { :locale => ["en"], :formats => ["html"] } ) Tuesday, April 24, 12
63. ActionView::LookupContext lookup_context.find( "page", # name ["foo"], # prefixes false # partial ) # will find views/foo/page template # # or raise # # ActionView::MissingTemplate Tuesday, April 24, 12
64. ActionView::Renderer Tuesday, April 24, 12
65. ActionView::Renderer Surprise! Tuesday, April 24, 12
66. ActionView::Renderer Surprise! Responsible for rendering. Tuesday, April 24, 12
67. ActionView::Renderer renderer = ActionView::Renderer.new(lookup_context) renderer.render(context, :template => "page") Tuesday, April 24, 12
68. Context? Tuesday, April 24, 12
69. Context? View needs to be rendered in some kind of context that provides methods and instance variables Tuesday, April 24, 12
70. ActionView::Context Tuesday, April 24, 12
71. Wrapping up Tuesday, April 24, 12
72. Wrapping up Template is found by ActionView::LookupContext, rendered by ActionView::Renderer in context of ActionView::Context (which typically is ActionView::Base) Tuesday, April 24, 12
73. WebMachine gist.github.com/2287909 Tuesday, April 24, 12
74. WebMachine class PageResource < Webmachine::Resource def resource_exists? slug = request.path_info[:slug] @page = Page.first(:slug => slug) @page.present? end def to_html "<html><body>#{@apge.title}</body></ html>" end end Tuesday, April 24, 12
75. WebMachine + ActionView class AbstractResource < Webmachine::Resource def view_context @_view_context ||= begin ActionView::Base.new(renderer, assigns, self) end end def lookup_context @_lookup_context ||= ActionView::LookupContext.new(paths) end def renderer @_renderer ||= ActionView::Renderer.new(lookup_context) end def paths ActionView::PathSet.new(["views"]) end end Tuesday, April 24, 12
76. WebMachine + ActionView class PageResource < AbstractResource def resource_exists? slug = request.path_info[:slug] @page = Page.first(:slug => slug) @page.present? end def to_html renderer.render(view_context, :template => "page") end def assigns { :page => @page } end end Tuesday, April 24, 12
77. WebMachine + ActionView <!DOCTYPE html> <html> <head> <title><%= @page.title %></title> </head> <body> <h1><%= @page.title %></h1> <article><%= @page.content %></article> </body> </html> Tuesday, April 24, 12
78. What if I want to stop using assigns? gist.github.com/2472931 Tuesday, April 24, 12
79. WebMachine + ActionView class AbstractResource < Webmachine::Resource include ActionView::Context def paths ActionView::PathSet.new(["views"]) end def lookup_context @_lookup_context ||= ActionView::LookupContext.new(paths) end def renderer @_renderer ||= ActionView::Renderer.new(lookup_context) end end Tuesday, April 24, 12
80. WebMachine + ActionView class PageResource < AbstractResource def resource_exists? slug = request.path_info[:slug] @page = Page.first(:slug => slug) @page.present? end delegate :title, :content, :to => "@page" def to_html renderer.render(self, :template => "page") end end Tuesday, April 24, 12
81. WebMachine + ActionView <!DOCTYPE html> <html> <head> <title><%= title %></title> </head> <body> <h1><%= title %></h1> <article><%= content %></article> </body> </html> Tuesday, April 24, 12
82. The caveat with such approach: helpers are not available by default Tuesday, April 24, 12
83. DIY Tuesday, April 24, 12
84. Read the code DIY Tuesday, April 24, 12
85. Read the code DIY Use a debugger Tuesday, April 24, 12
86. Read the code DIY Use a debugger Play with the code Tuesday, April 24, 12
87. And buy this book: Tuesday, April 24, 12
88. Journey! set = Journey::Routes.new router = Journey::Router.new(set, { :parameters_key => "rack.request.query_hash" }) strexp = Journey::Router::Strexp.new( "/foo/:id", # path { :id => /\d+/ }, # requirements %w(/ . ?)) # separators path = Journey::Path::Pattern.new(strexp) set.add_route App, path, {:request_method=>/^GET$/}, {:foo => true} Tuesday, April 24, 12
89. Journey! Router = lambda do |env| router.call env end App = lambda do |env| key = "rack.request.query_hash" body = "#{key}: #{env[key].inspect}" [200, {}, body] end run Router Tuesday, April 24, 12
90. localhost:3000/foo/1 response: rack.request.query_hash: {:foo=>true, :id=>"1"} Tuesday, April 24, 12
91. gist.github.com/2483024 Tuesday, April 24, 12
92. gist.github.com/2483024 Tuesday, April 24, 12
93. bit.ly/using-rails-without-rails Tuesday, April 24, 12
94. Summary Tuesday, April 24, 12
95. Thank you Tuesday, April 24, 12
96. Questions? Tuesday, April 24, 12
97. bit.ly/using-rails-without-rails Tuesday, April 24, 12