How to work with the Old Book and New Code for 2.0.2

Rails
1

Hi,

I own few good books based on rails 1.2. Its good enough but now
outdated
since many things have changed from 1.2 to 2.0.2

I have downloaded the codes in 2.0.2.
But I am confused, how should i read the book and work with new codes.

Are there any major changes in rails 2.0.2, except Scaffolding and
Routing…?
What should i read from old and famous books for rails 1.2…?
Will my knowledge for rails 1.2 will go waste, if i read those books.

I am sure, many would have faced the same situation. I would like to
know the best method for this.

Thanks.

2

Hi, Rahil
I suppose there are no major changes between these two versions other
than as you mentioned. Remaining changes are only about the syntax.
You can always refer the following link for the purpose

http://www.buildingwebapps.com/

On Jun 5, 3:48 pm, Rahil K. [email protected]

3

Read your book, then go lookup the technique the book describes in the
api (api.rubyonrails.org) and check for differences.

Taht way, you should still get the benefit of the structured message
from the book and see what the current implementation requires.

4

I’d suggesting buying the beta book of Agile Web D. with
Rails, which has been largely updated for 2.0.2 and should save you
considerable time.

I have a list of books that are updated for 2.0 at
http://www.buildingwebapps.com/articles/27

Michael S.
www.BuildingWebApps.com

On Jun 5, 3:48 am, Rahil K. [email protected]

5

If you read ryandaigle.com youll be fine

On Jun 5, 2008, at 5:48 AM, Rahil K.
<[email protected]

6

OOps…

I missed out the Important topic like REST with Rails 2.0.2.

None of the old book will teach me REST.

Can some one help me out pointing Good Blogs/Tutorials links on REST.

Thanks

7

I had/have the same problem, but the main thing is that you just try
out stuff and then use the book as a reference for ideas on how to
handle different problems. Checking out http://pragprog.com and
picking up the Beta PDF of Agile Web D. with Rails would be a
good place to start, and I also recommend two other books, The Art of
Rails and Simply Rails 2.

Main thing is to use everything, question everything, and fail a lot.
That’s why we use version control.

On Jun 6, 12:46 am, Rahil K. [email protected]