Thanks =) good work!

Typos and etc. throughout.

Hi pleabargain, 

I had a quick look through your ebook and I like it, especially the choice of topics. It seems to duplicate some basics that are available elesewhere, I guess that's because you want to create a `complete' work that does not rely on additional tutorials to get a beginner started. I can see that your ebook would work very well with my students!

I hope you keep worrking on in it and I would like to make one suggestion: don't widen the scope in future versions! Instead it might be interesting to add a few more hackish examples to the topcis you already included. Typically that's what can be found on the Wiki or here, but I'd like to see some more of such code examples in the more structured context of a book.

Andreas

I had visited your links but when I opened it. It doesn't load your page.

Needs a good copyedit.  Just glanced at Chapter 3 - here is an example.

At first i wanted to name the chapter "If things go wrong" but that didn't feel right , because it is not a question IF but only a question WHEN things go wrong. They will for sure, when you least expect it, and you will have no clue what to do.
Hope i didn't scare you to much, but so it is. In this section i will show you some of the most common failures that can (and mostly will) occure when writing computer programms. It will give you some starting points to look for when something doesn't work the way you expected. But be prepared for the unexpected, since errors are very creative little monsters that try to catch you wherever they can.

Quick rewrite..

At first , I wanted to name the chapter "If things go wrong", but that didn't feel right. It's not a question of IF things will go wrong, but WHEN. They will for sure, when you least expect it, and you will have no clue what to do.
Hope I didn't scare you too much, but so it is. In this section , I will show you some of the most common failures that can (and most likely will) occur when writing computer programs. It will give you some starting points to look for when something doesn't work the way you expected. But be prepared for the unexpected, since errors are very creative little monsters that try to catch you wherever they can.

Very good. I am looking forward to seeing the new version. Typically I have let students use Processing during summer projects and I am planning to use your ebook in the future. I'll let you know what the students say about it.

Andreas

On December 24 I released the first beta version of
my Processing Ebook. Now I corrected countless errors and typos,
added some of the missing screenshots and started to check all the code examples (special thanx to Ersin Kurun and Dennis Daniels for the corrected and annotated versions).

I uploaded the next beta version to the project page.

Changes I made in this version:

• corrected countles typos and spelling errors
• added missing screenshots
• fixed the code examples in the game chapter
• removed the "extending" chapter - I think it is to complicated for a beginner. I plan to make a seperate tutorial from this chapter

I'm still not sure about the 3D chapter. Maybe I kick it too in the next version. I'm also planning to support other formates like
html, epub, mobi ...

I still would like to receive feedback, hints, annotations, suggestions, ...