Line by line explanations for new topics and making things more visual

[Spencer]

Hi,

I'm enjoying the book and feel that I'm making good progress - however there are a few things that might be helpful - especially at the beginning of the book;

For a new excercise or method etc.; have the code on the left as per usual - and on the right: an explanation of what that line is doing.
                                                     not for every excercise but at the beginning of a new chapter. This would be helpful for identifying
                                                     elements of code that are needed but not going to be explained until later in the book or at all.

Make things a bit more visual;         It would be great to have a few really clever diagrams that depict the relationship between
                                                    different elements of code like objects and methods - but also for entire (small ) programs that
                                                    illustrate the flow of the program.

Obviously, I'm new at this and may be suggesting things that: to an expert may not be practical - but I'd still like to see them

Thanks for listening!

Regards,
Spencer.

[KinAZ]

I like these suggestions.

And I'll add one more: Consider adding a few more exercises at the end of each chapter

[Robocub]

I totally second Spencer's suggestion. I think its a great idea and would be really helpful for those code-challenged like me.  I'm a fairly visual guy and pictures speak a thousand words sometimes.  I know this forum has the reference Language Summary but this is very wordy and not a simple reference to glance at.

[skochan]

There will likely be a third edition to this book at some point.  I'll be sure to take these ideas into account.

Cheers,

Steve Kochan