From: gsm.beamon@...
Date: 2006-10-19T08:50:06+09:00
Subject: Re: Partial Resolution?

> Crystal balls help. I feel the pain. Sadly enough, irb, listing methods
> of an object interactively, and then wading through docs to guess where
> they are defined are your only salvation. Basically, hope you never have
> to use more of libraries like this than you can keep in your head after
> learning them, or that someone does Cruel and Unusual things to rdoc to
> let it figure out these shenanigans.
>
Thank you.

Ruby Community: why doesn't RDOC tell you all the includes or requires?
I mean if ApplicationController::Base said that it included files
<....> then I could have put two
and two together.

My only problem --- which I belatedly solved and which was immediately
pointed out
by another poster --- is that I was looking in the wrong files. Had I
kept on looking I
would have found even more files that evenutally defined the class and
included
ApplicationController::Layout which presumbably includes
ApplicationController::Layout::
ClassMethods. And volia there's layout().

The connection is important. This seems obvious to me. But other
posters have
said, "Hey, I found it not problem in .../layout.rb. So what's the
deal?" The deal is
that this:

class ApplicationController < ActionController::Base
    layout "standard"
end

Why is should anybody jump and then why is it correct to jump from
ActionController::Base to ActionController::Layout::ClassMethods per
.../layout.rb?
That isn't answered by merely pointing .../layout.rb.