tag:blogger.com,1999:blog-7531303471386503232.post3831567326267948859..comments2016-02-16T05:42:11.273-05:00Comments on Are You There God, It's Me David Stacey Joerg: Ruby/Rails is confusing for noobsAnonymoushttp://www.blogger.com/profile/17286870671432994638noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7531303471386503232.post-53352191142633613332012-01-27T16:24:34.039-05:002012-01-27T16:24:34.039-05:00Thanks Jeff!Thanks Jeff!Anonymoushttps://www.blogger.com/profile/17286870671432994638noreply@blogger.comtag:blogger.com,1999:blog-7531303471386503232.post-34294447370921249032012-01-27T12:23:36.136-05:002012-01-27T12:23:36.136-05:00Some answers:
As far as documentation goes you ca...Some answers:<br /><br />As far as documentation goes you can find old versions of both the api and the guides at urls like so:<br /><br />http://guides.rubyonrails.org/v3.1.1/<br /><br />where v3.1.1 is the version number.<br /><br />Stick with ERB, it makes things much easier, because it is closer to the final output in syntax.<br /><br />Once you scaffold, you have to manually update the files, mostly as you get depper in you'll stop scaffolding so much and just rely on convention.<br /><br />And finally the asset pipeline, ah the asset pipeline. Prior to 3.1 assets were served directly from the /public/ path so <%= image_tag 'rails.png' %> would serve from /public/rails.png. They changed all that and now it looks for /app/assets/rails.png, or /public/assets/rails.png It is really confusing, and a breaking change, and i wish they hadn't, anyway you can see how the webserver-rails boundary works here:<br /><br />http://guides.rubyonrails.org/v3.1.1/asset_pipeline.html#coding-links-to-assets<br /><br />Hope that helps, most of the stuff on internet is old and dated right now -- 2008 was the banner year for rails blog posts -- so it is hard to find resources outside of the guides and reading the source. Best of luck!Jeff Larsonhttps://www.blogger.com/profile/02962266926078103520noreply@blogger.comtag:blogger.com,1999:blog-7531303471386503232.post-20941087424393921652012-01-27T11:40:19.904-05:002012-01-27T11:40:19.904-05:00A kind RoR expert referred me to the Pragmatic Pro...A kind RoR expert referred me to the Pragmatic Programmer books. Many of them are published before 2010, which means they are certain to be out of date in material ways.<br /><br />The first Pragmatic Programmer book listed on Amazon is Agile Web Development with Rails. A commenter about it points out "... Rails 3 is changing fast and might not settle down for a little while. A good portion of this book is obsolete. For example, this book still teaches readers to use the Prototype library even though Rails is switching to jQuery in 3.1. Additionally there are numerous other large changes in Rails 3.1 that are not mentioned in this book that will be essential for future Rails developers."<br /><br />Argh.Anonymoushttps://www.blogger.com/profile/17286870671432994638noreply@blogger.com