Are there any other tutorial than “Agile Web D. with Rails”
that you can suggest? So far I can’t say that RoR has been easy to
learn. 
Can you list some specific areas where you think you need some help? I’m
sure that folks can point you in the right direction if you can let us
know
where you think you need help.
I would really recommend digging into Ruby… understanding the language
itself is vital if you want to do more complex applications. It also
might
make some of the conventions used by Rails a little more clear.
Are there any other tutorial than “Agile Web D. with Rails”
that you can suggest? So far I can’t say that RoR has been easy to
learn.
Well, the Agile book is probably the most thorough released book, but
if you want web-based tutorials, this is a good place to start:
This was posted a few months ago. There is a lot of momentum behind
Rails development, so you may find tutorials that are even a few
months old a little dated. But you should start with the basics
anyway. Worry about the latest features after you have a good
grounding.
-TJ
Pål,
MVC concept. What I don’t understand is how to build using the different
classes that I find here http://api.rubyonrails.org/? And what is
http://corelib.rubyonrails.org/ and http://stdlib.rubyonrails.org/?
The API docs are better left for reference once you’re heads-down
coding your own ideas. I think they’d be overwhelming as a starting
point.
I hate to harp on the Agile book, but the 2nd edition beta has a
completely reworked and updated “Building An Application” section. I
think if you follow along with that and type the code in by hand (no
cut and paste!) and understand the basic concepts behind the code,
you’ll be in good shape to get your own apps going. Then, the API docs
will reveal their value as a reference.
Good luck!
-TJ
Brian H. wrote:
Can you list some specific areas where you think you need some help? I’m
sure that folks can point you in the right direction if you can let us
know
where you think you need help.I would really recommend digging into Ruby… understanding the language
itself is vital if you want to do more complex applications. It also
might
make some of the conventions used by Rails a little more clear.
I’ve started to do that, digging into Ruby that is. And this is the easy
part, and what tells me that the effort of learning Ruby over php will
be well invested time.
What I don’t get is the how structure works in more detail. I get the
MVC concept. What I don’t understand is how to build using the different
classes that I find here http://api.rubyonrails.org/? And what is
http://corelib.rubyonrails.org/ and http://stdlib.rubyonrails.org/?
In both PHP and Lasso there is a manual to look into when needed. In
that sense they have both been much easier to learn. You read and build.
I hope you understand. It feels like there is some part missing in the
explanations I’ve read. Could also be that I’m not that familiar with
classes in general, which seems to be the essential part in RoR.
On 6/14/06, Pål Bergström [email protected] wrote:
I hope you understand. It feels like there is some part missing in the
explanations I’ve read. Could also be that I’m not that familiar with
classes in general, which seems to be the essential part in RoR.
I see this as the core challenge of anyone coming straight over from
PHP to RoR. PHP is not an object oriented language. And RoR does a
lot of magic behind the scenes. It generates classes and objects
and a load of stuff. It’s amazing really, when you know what’s going
on behind the scenes. Most common web frameworks give you hashes or
arrays of hashes or arrays of primitive types.
RoR gives you hashes or arrays of objects. It’s sometimes difficult
to know what goes where and how without understanding classes and OOP
in general.
I second the AWD book approach. Work through the book. Read the
second half, sleep with it under your pillow, take it in the shower
(waterproof covering recommended), hire Kelsey Grammer to read it onto
tape for the morning and evening commute. Eat it, breathe it, live
it… And then the core documentation will make much more sense. If
you still have problems with classes or the core documentation, then
do the same with the “pickaxe” Ruby book.
When you understand Ruby, you will understand Rails. I think it’s
even more essential for those with a non-OOP background to understand
Ruby. You may be able to take a shortcut on that if you know another
OOP language. If not, the time invested in learning OOP (particularly
the Ruby color) will flow back hundreds-fold.
-Curtis
While we’re talking books, I would also recommend Ruby for Rails by
David Black. Outstanding book for those new to both Rails and Ruby,
which is most of us I’m guessing. It’ll help you understand both Ruby
and Rails in the context of each other.
-TJ
On 6/14/06, Dark A. [email protected] wrote:
I’m a complete newb so what do I know but I came across this book the
other day (still in beta) Mr. Neighborly’s Ruby and Rails. look under
the wiki/ books. The first chapter is downloadable at no cost and
it’s 71 pages of basic Ruby.
Yup yup. A very good Ruby reference for quick-to-speed Railers… 
The entire book is $9, almost less than a trip to a decent fast food
place. 
http://www.rubyonrailsbook.com/
-Curtis
I’m a complete newb so what do I know but I came across this book the
other day (still in beta) Mr. Neighborly’s Ruby and Rails. look under
the wiki/ books. The first chapter is downloadable at no cost and
it’s 71 pages of basic Ruby.
Anyway, I’m not connected to the author but thought that this book
seems to have a great value but is not shown on the ror main page like
that others.
Stuart
Curtis S. wrote:
On 6/14/06, Dark A. [email protected] wrote:
I’m a complete newb so what do I know but I came across this book the
other day (still in beta) Mr. Neighborly’s Ruby and Rails. look under
the wiki/ books. The first chapter is downloadable at no cost and
it’s 71 pages of basic Ruby.Yup yup. A very good Ruby reference for quick-to-speed Railers…
The entire book is $9, almost less than a trip to a decent fast food
place.http://www.rubyonrailsbook.com/
-Curtis
This was very good. I’ll buy it. Thanks
Carl F. wrote:
I thought one of the best Rails tutorials was the Apple tutorial:
http://developer.apple.com/tools/rubyonrails.html
One of the uber cool parts about PHP is that the docs are searchable.
This is missing in the default Rails api, but there is hope:
Thanks.
“Pål” == Pål Bergström [email protected] writes:
Are there any other tutorial than “Agile Web D. with Rails”
that you can suggest? So far I can’t say that RoR has been easy to
learn.
Oh, it’s easy to learn – if you know the foundations it builds on. If
you don’t it’s going to about as hard as building a house from the
roof down.
From your posts here, I get a string impression that you are not
familiar with at least some of the basic foundations on which Rails is
built. You do need to know object-oriented programming, because Rails
uses that a lot. You do need to know how HTTP works on a basic
level, because occasionally Rails uses it in a not-so-basic way.
–
Calle D. [email protected]
http://www.livejournal.com/users/cdybedahl/
“You know, if I garbage collected my brain I wouldn’t have anything
left.”
– Paul Tomblin, BofhNet
Calle D. wrote:
“P�l” == P�l Bergstr�m [email protected] writes:
Are there any other tutorial than “Agile Web D. with Rails”
that you can suggest? So far I can’t say that RoR has been easy to
learn.Oh, it’s easy to learn – if you know the foundations it builds on. If
you don’t it’s going to about as hard as building a house from the
roof down.
Everything is relative.
I thought one of the best Rails tutorials was the Apple tutorial:
http://developer.apple.com/tools/rubyonrails.html
One of the uber cool parts about PHP is that the docs are searchable.
This is missing in the default Rails api, but there is hope: