Dmitri Zagidulin

Thanks, very much appreciate it.

On the one hand, I like this idea (of automatically generating a list of tool descriptions with pragmas). On the other, I'm not sure how useful it will actually be,...

Also: move the 'Versions of a method' section to the new Sharing Code and Source Control chapter.

Sounds good to me.

Consensus is to use the code font Pillar syntax for referencing menu items in the book. To do: 1. Change bold markup for menu items, like ``""Accept it""` to monospace,...

Also, why does `download.sh` seem to download sources for old Pharo versions? ``` Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/mac/stable.zip pharo-vm/Pharo.app/Contents/MacOS/Pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Downloading PharoV30.sources: http://files.pharo.org/sources//PharoV30.sources.zip Downloading PharoV40.sources:...

Agreed that we should introduce the Configuration browser early on. (And, yeah, Metacello can be left for Deep Into Pharo. Using packages is pretty fundamental, writing/editing packages is definitely an...

Sure, agreed. Although, why create a separate chapter? All of the things you mention (Versioner, SH and GH, etc) all belong in the existing Source Control and Sharing Code chapter.

Perfect, thanks! :)

It turns out that there are updated One-Click experience images, for Pharo 4 + Seaside 3.1! I updated the installation instructions to use them. Still need to add manual installation...