I’m delighted to announce that Chad F.'s new book, Rails Recipes,
is now available
as a Beta Book.
This is a great title for folks who know Rails, and for folks who
want to get the most out of Rails. It contains detailed recipes for
doing real-world things with Rails, all illustrated with working
code. Some examples are drawn from Rails 1.1, the rest from Rails 1.0.
If you’re used to other recipe-style books, you’ll be surprised by
the depth Chad goes to in this book. These aren’t the usual “How to
substitute a string into a template” recipes. Instead, you’ll find
code to solve the kinds of problems you face in real applications:
using multiple databases, handling sortable lists, using tags, and
many, many more.
Right now, we’re about 1/3 done. The current beta PDF contains 21
recipes: we’ll be growing it to about 70 recipes over the coming
months. As well as the opportunity for the usual great feedback, one
reason we’re releasing this early is to solicit ideas for other
recipes folks would like to see.
As always with our Beta Books, you’ll be able to get lifetime updates
to the PDF, both during the beta process and for the life of this
edition of the book. If you also order the paper book, it’ll ship
just as soon as we have it in stock (probably sometime in May or
June, but you know what authors are like…)
You can buy the book via http://pragmaticprogrammer.com/titles/fr_rr
Thanks
Dave
Excellent ! Geat job Chad and team !! Keep em’ coming 
Looking forward to reading this. Thank you
Sincerely,
PJ Hyett
Just downloaded it Dave. Where would you like ideas for other recipes
sent
to? You see a lot of repeating patterns here on the list and it would be
nice to have those covered as well if possible.
Bob S.
http://www.railtie.net/
On Feb 2, 2006, at 11:58 PM, Chad F. wrote:
Please send any ideas you have. I’d be delighted to hear from anyone
who has recipe ideas. The best address is chad @ chadfowler.com
Hey Chad. Great book. I have an idea for a recipe.
I want to develop a web app that will make me a lot
of money. Can you show the recipe that will let me
do that? Oh, can you make it in less than 100 LOC.
I don’t have a lot of time to type it in.
;>)
Seriously, I’m looking forward to reading what you have so far.
Jim F.
On 2/2/06, Bob S. [email protected] wrote:
Just downloaded it Dave. Where would you like ideas for other recipes sent
to? You see a lot of repeating patterns here on the list and it would be
nice to have those covered as well if possible.
Bob S.
http://www.railtie.net/
Hi Bob. Thanks for downloading the book!
Please send any ideas you have. I’d be delighted to hear from anyone
who has recipe ideas. The best address is chad @ chadfowler.com
Thanks!
–
Chad F.
http://chadfowler.com
http://pragmaticprogrammer.com/titles/fr_rr/ (Rails Recipes)
http://pragmaticprogrammer.com/titles/mjwti/ (My Job Went to India,
and All I Got Was This Lousy Book)
http://rubycentral.org
http://rubygarden.org
http://rubygems.rubyforge.org (over one million gems served!)
Wow, I am already loving this book. Chapters 11 and 12 are worth the
price alone. There are several tutorials on the web and on the wiki
and so forth, but sometimes that’s the problem–which method do you
choose?
I also love looking into the process behind writing the book. This
made me laugh out loud (page 61):
If no matching Right is found, a message is put into the flash, and
the browser is redirected to either the page from which it came (if
any) or the application’s unprotected home page (see rec.named.routes,
on page ??) as defined in fig.missing, on page ??.
Keep up the good work!
Sean
On 2/2/06, Jim F. [email protected] wrote:
do that? Oh, can you make it in less than 100 LOC.
I don’t have a lot of time to type it in.
;>)
Hey Jim! I’m afraid that if you want to make a lot of money with
Rails you’re going to need to type at least 500 lines if not 600
lines of code. Sorry. 
Chad F.
http://chadfowler.com
http://pragmaticprogrammer.com/titles/fr_rr/ (Rails Recipes)
http://pragmaticprogrammer.com/titles/mjwti/ (My Job Went to India,
and All I Got Was This Lousy Book)
http://rubycentral.org
http://rubygarden.org
http://rubygems.rubyforge.org (over one million gems served!)
On 2/3/06, Sean H. [email protected] wrote:
Wow, I am already loving this book. Chapters 11 and 12 are worth the
price alone. There are several tutorials on the web and on the wiki
and so forth, but sometimes that’s the problem–which method do you
choose?
Thanks so much! I’m very happy that you’re getting a lot out of it.
I’m very proud of what we’ve got so far, and I can’t wait to see what
comes out of the feedback from the Beta process. It’s my first time
doing a Beta book and I believe it’s going to have a profound impact
on the quality of the finished book.
I also love looking into the process behind writing the book. This
made me laugh out loud (page 61):
If no matching Right is found, a message is put into the flash, and
the browser is redirected to either the page from which it came (if
any) or the application’s unprotected home page (see rec.named.routes,
on page ??) as defined in fig.missing, on page ??.
Oops! todo_list <<
Chad
Chad F.
http://chadfowler.com
http://pragmaticprogrammer.com/titles/fr_rr/ (Rails Recipes - In Beta!)
http://pragmaticprogrammer.com/titles/mjwti/ (My Job Went to India,
and All I Got Was This Lousy Book)
http://rubycentral.org
http://rubygarden.org
http://rubygems.rubyforge.org (over one million gems served!)
On Feb 3, 2006, at 20:19, Chad F. wrote:
doing a Beta book and I believe it’s going to have a profound impact
on the quality of the finished book.
I am eager to buy the beta version, but if I read the book from cover
to cover and next week a new revision is out, will you publish
somewhere the delta so one can incrementally stay in sync?
– fxn
On Fri, 3 Feb 2006 21:16:05 +0100, Xavier N. wrote:
I am eager to buy the beta version, but if I read the book from cover
to cover and next week a new revision is out, will you publish
somewhere the delta so one can incrementally stay in sync?
+!! I’ve been keeping up on the Agile Web book, and although I realize
the
errata provide some of the info, the lack of a full changelog is
frustrating. I even tried doing an Acrobat diff one time (I’ve got the
full version), but after letting it sit and think for an hour, I gave
up…
Jay L.
On Feb 3, 2006, at 2:16 PM, Xavier N. wrote:
I am eager to buy the beta version, but if I read the book from
cover to cover and next week a new revision is out, will you
publish somewhere the delta so one can incrementally stay in sync?
Low level changes (bug fixes) are tracked on the errata pages.
High-level changes (new material) is mentioned in the announcements
of new betas.
Some stuff will probably fall between the cracks, but finding it will
be part of the joy of reading
Dave
Purchased Book and downloaded.
But just curious that will any update i will receive automatically to my
email or need to check web site regularly?
This is the first book I’m purcashed under beta programme so curious.
-Niket P.
On 2/3/06, Dave T. [email protected] wrote:
If you’re used to other recipe-style books, you’ll be surprised by
recipes folks would like to see.
Thanks
Dave
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
–
Best Regards,
Niket P.
For NexusNeo Exim
(A Div of NexusNeo System & Exim Pvt. Ltd)
Tel: +91 79 23244557
Fax: +91 79 23246531
E-mail: [email protected]
Web: www.nexusneo.com
Hey Jim! I’m afraid that if you want to make a lot of money with
Rails you’re going to need to type at least 500 lines if not 600
lines of code. Sorry.
This sounds like a challenge to me 
(An entirely possible challenge, with Rails and just a bit of
golfing.)
Tom
Dave
> Low level changes (bug fixes) are tracked on the errata pages.
See the many reports in this list and over time: the erratas pages is
confusing/completely useless.
And it’s surprising, seeing how well rounded is everything else in the
beta book experience.
A little redesign of this page is all that’s needed, but it’s badly
needed.
Alain
On Feb 4, 2006, at 12:59 AM, Xavier N. wrote:
With the errata page you don’t know what has been fixed for which
revision. The very third column label is confusing because it
mentions “fixed” and “reported”! Revisions are a great innovation,
but to round the circle from a user’s view a changelog of some sort
is needed. I bet they have the info, maybe is only that errata page
that IMHO has to be redesigned.
The ‘reported in’ field is the version of the book that is know to
contain the error, and the ‘fixed in’ field is the version that
contains the fix.
So, if you previously had (say) P1.2, and you want to know what’s
different in the very latest version, select P1.2 in the drop-down
list at the top of the page, and view all the errata marked as ‘fixed’.
Dave
On Feb 4, 2006, at 2:12, Jay L. wrote:
the
full version), but after letting it sit and think for an hour, I
gave up…
I have the same experience. I think this is something to be improved
in their flow of publishing.
With the errata page you don’t know what has been fixed for which
revision. The very third column label is confusing because it
mentions “fixed” and “reported”! Revisions are a great innovation,
but to round the circle from a user’s view a changelog of some sort
is needed. I bet they have the info, maybe is only that errata page
that IMHO has to be redesigned.
– fxn
On Feb 4, 2006, at 4:01 AM, Alain R. wrote:
Dave
> Low level changes (bug fixes) are tracked on the errata pages.
See the many reports in this list and over time: the erratas pages
is confusing/completely useless.
And it’s surprising, seeing how well rounded is everything else in
the beta book experience.
A little redesign of this page is all that’s needed, but it’s badly
needed.
Tell me what’s needed, and I’ll look into it.
Dave
> Tell me what's needed, and I'll look into it.
There should be a simple way to print a clean - long - page with all the
changes that apply to a pdf version.
Currently, everything is mixed up -errors, typos, suggestions etc…- and
the last column is cryptic and confusing (fixed In, fixed On).
I’ve printed, bound and heavily annotated version 2.0 of the pdf, so I
don’t plan to replace it soon. I’d like to correct the errors though,
hence my wish for a way to track them easily.
Alain