RailsCasts Pro episodes are now free!
Learn more or hide this
GitHub User: svyatogor
Thank you Ryan, I am very excited about Rails 4 and can't wait for it to hit at least pre release.
With all these changes under the hood do you expect it to be tough switching from Rails 3? Or the transitions this time should be smoother than from Rails 2.x to 3.x?
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.
Found a very weird bug, maybe it is actually poltergeist related. While I haven't had time to fully investigate it here is what happens:
.. here I do routine to login as a valid user, which works...
boom, after the second visit I find that that I am logged out, current_user is nil.
If, on the other hand instead of doing the second visit call I use respective click_link sequence everything works like a charm.
If you are using twitter bootstrap in your app you might find this calendar very handy: http://www.eyecon.ro/bootstrap-datepicker/ It integrates nicely with bootstrap design and seems to have the same functionality as the one from jquery ui.
I know it is rather controversial but I found RubyMine IDE to be a great way to debug rails apps. It has very cool UI for debugger with breakpoints, visual stack and so forth.
Fantastic screencast Ryan! So many rails developers are bewildered by the deployment process or have no idea how to setup the stack from scratch.
While capistrano is indeed a great tool and allows you to maintain very complex setups, but overtime found it to overkill for simple webapps with just single production server and maybe a staging server. Having tried heroku I really think git is the way to go in this case. Setting up post–receive hook on the the server is really very simple and all your deployment boils down to running 'git push production localbranch:master'.
With regards to unicorn I really see no reason you chose it as oposed to phusion passenger. It is an extra dependency that needs to be maintained. For me the beauty of using passenger lies in the fact that I don't need to maintain a separate service and make sure it is running at all times.
Nice an neat except for this trick with multiple scroll events being triggered. I think it would be much cleaner to unbind the scroll event till we get the results and once more products are loaded, bind it again.
Slightly OT question. Where did you get this comprehensive list of states/countries? I know many sources but they all require fair amount of work to import in rails db.
I think this a bit of a stretch... while there might be some situations when this kind of mojo would be helpful I don't it should be normal practice. In fact it breaks the MVC somewhat. What I normally do is one of two things: either app is fully JS–based and logic is processed via JS while rails acts as server side model or use ajax to fetch pre–processed data and only display them via js code.
Great timing, I was just investigating the topic as I start witching to ruby 1.9 and wanted to keep that as painless as possible.
Can't wait for the deployment screencast now!
Why should it? HAML is just templating language so you would just use same methods in HAML syntax from the view.