#397 Action View Walkthrough pro
Dec 09, 2012 | 15 minutes | Views, Code Walkthrough
Find out exactly what Rails is doing under the hood when it renders a view template for a response. What object context handles the template? How does the lookup process work? That and more covered in this code walkthrough.
- source codeProject Files in Zip (30.1 KB)
- mp4Full Size H.264 Video (46.2 MB)
- m4vSmaller H.264 Video (25.4 MB)
- webmFull Size VP8 Video (24.3 MB)
- ogvFull Size Theora Video (68 MB)
I love your videos, however this video and even the controller walkthrough were extremely fast and jumped around too quickly. I just couldn't focus on what you were saying. It seemed like I was just trying to figure out what directory you were in the entire time and not paying attention to the code.
I must say that I have only been working with Rails for only 8-10 months now.
I agree with with David
I am sorry to say but the walkthrough videos aren't the best of your creations. What I value a lot in your normal screencasts is that they scratch a very specific itch and show how to integrate thing that wouldn't otherwise be obvious.
I am not sure which purpose the walkthroughs server though. They are very generic, moreover experienced rails devs can read the code and figure this stuff out. Novice developers will feel lost anyway.
Ryan, Over the years, I have benefitted from your RailsCasts a lot. So I say this with nothing but sincere appreciation for what you have done and are doing for the Rails community. I totally second Sergey Kuleshov is saying above.
Please focus on specific topics that can be useful for a Rails developer and leave the innards of Rails to the Rails core team members and others who might be interested.
It's been my experience that understanding the inner workings of frameworks is exceptionally valuable for figuring out why things aren't behaving the way you expect them to.
It's true that understanding the inner workings of frameworks is very valuable. I was quite excited when I saw this railscast for that very reason. The problem is that zipping through a large number of classes & modules scattered about a number of unfamiliar files at high speed is simply not useful in learning Rails internals.
I agree with Tony, I like these walkthroughs, learn a lot on in and out of Rails. Actually I rather have video where we talk about smaller sections instead of a large topic of view/controller walkthrough it's just too much information crammed into a short video
I must say that I completely disagree with these latest sentiments. I think that every developer should spend time understanding the tools that they use (which INCLUDES reading the source code). I don't consider developers who use rails to be exempt to this.
Rails is complicated and intertwined (as you can see from the screencast). Most people, when first viewing the code get overwhelmed quickly. These walkthroughs show how you should read through source code and put together the pieces to gain an understanding of how things are put together.
I, for one, applaud the effort spent on more 'advanced' screencasts.
I completely agree with Kevin Webster, and I really appreciate Ryan's effort to talk about such an entangled subject in a short screencast like this one.
If he goes too fast, no one stops you from pausing the recording as much as needed.
thanks again Ryan for your execlent work
I also agree with Kevin. These walkthroughs are informative.
It is not that easy to trace through the source code just by reading it, so it is very helpful to see how Ryan navigates the code and what he focuses on in each class or method.
I concur with Kevin. I've come to Ruby & Rails with a background in other programming languages and frameworks (C, Perl, Scheme and Java). The rails API doco is somewhat half-baked, so I am very interested in deep-dive walkthroughs and I have no problem keeping up. And the pause button is there if one needs to chew on the substance a little more.
Maybe the walk through videos should be free.
I like the walkthroughs.
I love these, it helps me in finally understanding how you are supposed to use Rails instead of just following recommendations.