What do you think of this approach?
I think resources should be paid for (I just bought the peepcode videos from a comment here) I would be mildly worried that $49 might be a little high for some, but then again I hope I am wrong. Previews are always nice to see, the first couple of chapters to get a feel.
Definitely hear you (and others) on the previews - we agree they'll be good to have.
-- Credit Card * The transaction has been declined because of an AVS mismatch. The address provided does not match billing address of cardholder. --
Are you going to have easily-downloadable drafts of the book though? or will I have to compile it?
Sound like it'll work out?
I'm not 100% on the idea of one app for all the chapters. For books we've written and workshops we've delivered in the past, this has actually been more trouble than it's worth, and we ended up adding superfluous content in order to build a cohesive app.
We're aiming to have a code base delivered with the app where examples live, but the examples might not always cohere - we'd rather each example best illustrate its content.
While I don't necessarily have to take the concept as far as Hartl did for it to work, I would suggest that the code relating to every concept/portion of the book is capable of doing something in and of itself, regardless of how small.
Actually the Hello Backbone.js tutorial is a good example of this. http://arturadib.com/hello-backbonejs/ Every page works on it's own and build on the code from the page before.