Folks:
I’ve uploaded B1.21 of Agile Web D. with Rails.
I’ve spent the last two weeks applying copy edits and then doing the
book’s layout (I hope never to see a red pen mark again). This means
that the book should now be pretty close to its final form.
I know I have an outstanding issue with some hyperlinks between pages in
the PDF: I’m investigating this.
Also, it looks as if Rails 1.2 will not be ready in time for the
book to go to the printer. However, the book is written as if 1.2 was
already out.
To cope with this, I’m trying something a bit different. I’ve created
a bundle of the Rails source, and I’ve included instructions inside
the front cover of the book (page 2 in your PDF) on how to include
this bundle in your application. I hope this will tide us all over
until 1.2 becomes a reality (which should be in the next month or so).
Cheers
Dave
Congrats on the release candidate. The book has become both a
reference and walkthrough of unparallelled quality.
Dave,
Great work!
Before this is finalized, I’d like to renew my request to have roman
numeral pages distinguished from arabic numerals. It makes it real easy
to just type the page number and not not have to add the pages that
Preview counts.
Also, if you are collecting errata still, I believe observe_field with a
frequency of 0 or less is truly an onChange event rather than a
recurring one. That could be important to some.
Thanks again and regards,
Bill
On Nov 12, 2006, at 5:43 AM, devaulw wrote:
Before this is finalized, I’d like to renew my request to have roman
numeral pages distinguished from arabic numerals. It makes it real
easy
to just type the page number and not not have to add the pages that
Preview counts.
They used to be like that, but at some point during a software
upgrade that stopped being the case. Your post spurred me to dig into
this, and I think I worked it out: if you look at the latest beta,
you should find that page numbers are the same as PDF page numbers
(even though that leads us to the strange situation where the cover
is page number one 
Cheers
Dave
Dave T. wrote:
Also, it looks as if Rails 1.2 will not be ready in time for the
book to go to the printer. However, the book is written as if 1.2 was
already out.
Hi Dave,
Is it worth considering holding off for a simultaneous release alongside
1.2 ?
A.
On Nov 13, 2006, at 9:22 AM, Alan C Francis wrote:
Is it worth considering holding off for a simultaneous release
alongside
1.2 ?
I’m afraid we can’t change our dates. We booked press time months
ago, and arranged for the tons of paper to be there. When we
originally booked the slot, it looked as if 1.2 would have already
been out for months. Even a month ago, when we confirmed the time, it
looked as if 1.2 would be out in plenty of time. I’m still hopeful
that we’ll see 1.2 by the time the books start hipping (in mid
December).
I can’t speak for the core team, but one thing I think would help
would be for folks in the community to be more proactive in both
downloading the various beta gems and reporting on issues they find
in those gems. A new Rails release is a big responsibility, and I
think core would appreciate as much feedback as they can get prior to
the release–that added confidence would help them release early.
Your next chance to contribute to this process will be the release of
1.2RC1, the first 1.2 release candidate. I very, very much hope that
this will make an appearance this week, but that’s up to the core team.
Cheers
Dave
Dave T. wrote:
On Nov 13, 2006, at 9:22 AM, Alan C Francis wrote:
Is it worth considering holding off for a simultaneous release
alongside
1.2 ?
I’m afraid we can’t change our dates. We booked press time months
ago, and arranged for the tons of paper to be there. When we
originally booked the slot, it looked as if 1.2 would have already
been out for months. Even a month ago, when we confirmed the time, it
looked as if 1.2 would be out in plenty of time. I’m still hopeful
that we’ll see 1.2 by the time the books start hipping (in mid
December).
Thanks Dave, that clarifies things.
A.