Yes I think reducing screenshots makes sense, especially the ones that do not directly explain the tools. Reducing them will make it easier to update PBE in the future. I am also very interested in automating the screenshot process as has been suggested in another thread, if we able to do this that will reduce the time to update PBE in future massively.
I will try to simplify PBE so its much easier to update without sacrificing quality for the viewer. Obviously screenshots are essential. I am also viewing your TODO you have linked on the Readme. I have updated the Readme so that links to Damien's Documentation of Pillar and also to Pharo for the Enterprise , obviously anyone who wants to contribute must be aware of both of these things. I also added Chapter 1 - Quick Tour in Pharo. Just the first part , the chapter is of course still a WIP. I am not so sure what you mean about automated tests, are they for the example code ? I am all for automation. On Mon, May 5, 2014 at 11:08 PM, stepharo <[email protected]> wrote: > This is really cool that people want to update the Pharo by Example book. > This is a really an important task and it will have a real impact. > You can also reduce the number of screenshots or point related to the > interaction. > > What would be good is to make the automated tests working again because we > could spot > if we got some regressions. > > Stef > > > How I can help improve Pharo by Example , add chapters and update current >> ones for Pharo 3 ? >> >> What is the process ? >> > > >
