With the rate at which Rails is changing and a good chunk of the agile
rails book needing quite an overhaul to be updated to the current
version, wouldn't chapters in a book on the actual implementation of
(parts of) rails be even more prone to going out of date?  Writing a
book that contains this information is definitely interesting from a
code design perspective, but definitely not from a "this is how things
are implemented" in rails perspective.

I've written rails patches myself (including some for ActiveRecord)
and I gained a pretty good understanding from this exercise alone.  I
still recommend this approach to figuring out how ActiveRecord works;
you'll get to know parts of ActiveRecord quite intimately this way and
are always working with current code.

Just my 2 cents.

On 6/29/06, Hampton <[EMAIL PROTECTED]> wrote:
Pete-

I've been toying with a few chapters of a book to do just that.

About half is API and uses. Then the other half of the book explains *how*
it works. And some of the fun/cool tricks going on inside in the guts to
make the usibility so simple.

But, its quite a while from being done...

-hampton.


On 6/29/06, Peter Michaux <[EMAIL PROTECTED] > wrote:
> Hi,
>
> I've used Rails quite a bit. I want to understand the major Rails
> components well enough to read the Rails source without great
> struggle. Eventually I'd like to know how all the components are wired
> together but I'd be happy to start with understanding Active Record
> thoroughly. For me, the best way to understand something is to build
> it. I imagine building a simple version of Active Record with just one
> type of validation, one type of association, and one database adapter.
> A stripped down Active Record with the same file and class/module
> structure as the real thing. Does a tutorial about this sort of
> exercise exist? Would a tutorial about this be helpful for others? Is
> there anyone who can direct me to the most important parts of Active
> Record? (I've looked through David Black's book and it doesn't seem to
> cover the detail of Rails I'm interested in learning.)
>
> Thanks,
> Peter
> _______________________________________________
> Rails-core mailing list
> Rails-core@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails-core
>


_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core



_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to