# SquareBracketAssociates/PharoByExample-english

Open source LaTeX of Pharo By Example
TeX HTML Other
Latest commit ccd9ab9 Mar 24, 2015 Dmitri Zagidulin Merge pull request #20 from SmalltalkZen/dz_update_readme
Update README, point to Updated PBE
 Failed to load latest commit information. Admin BasicClasses Collections DBXTalk Environment Exceptions FAQ FirstApp Messages Metaclasses Model Monticello Morphic Omnibrowser Preface QuickTour Reflection Regex SUnit Seaside Streams Syntax figures .gitignore .svnignore Makefile PBE-Omnibus.bbl PBE-Omnibus.tex PBE-TO-DO.txt PBE1.bbl PBE1.tex README.markdown common.tex commonDemo.tex contributors.txt errata.txt examples.rb history.sh history.txt pbe1-examples.txt pbe2-examples.txt

# Pharo by Example

Note: This book is currently being revised and updated for Pharo 4 at Updated Pharo By Example (latest PDF).

Pharo by Example (vol 1) is a practical introduction for Pharo, a Smalltalk-inspired programming language, IDE and live coding enviroment.

This is the original LaTeX source repository of the Pharo by Example book, created for Pharo 1.4, and inspired by Squeak By Example (source code).

## Translations

There are translations PBE for the following languages (in various stages of completeness):

## Deep Into Pharo (Pharo By Example vol 2)

Deep into Pharo (source code) is the second volume of a series of books covering Pharo. Whereas the first volume is intended for newcomers, this second volume covers deeper topics.

## Contributing to Pharo by Example

Note: This book is no longer under active development. Please consider contributing to Updated Pharo By Example, instead.

To contribute to the book or to a translation project, please:

• subscribe to the [sbe-discussion] mailing list;
• clone the relevant repository and contact the lead person responsible;
• if you are unsure who is in charge, ask on the list;
• publish changes to your copy of the the repo and inform the lead to pull changes.

To start a new translation project:

• announce the start of the translation effort on sbe-discussion;
• people then will react and you find others who want to help;
• we will then add a repository to SquareBracketAssociates;
• we will list it on PharoByExample.org.

See PBE-TO-DO.txt for status of tasks for PBE 1.

## Contributing to Deep Into Pharo (Pharo by Example vol 2)

The source code for Deep Into Pharo is currently managed by SVN, and can be found at the Inria Forge Pharo By Example Two repository.

To contribute to the book or to a translation project (we should finish it first), please:

• subscribe to the [sbe-discussion] mailing list;
• register for Inria Forge (use RMOD as team) and send an email to sbe-discussion (we will add you to the PharoBooks project)
• if you are unsure who is in charge, ask on the list;
• checkout what you want: svn co https://xxxx@scm.gforge.inria.fr/svn/pharobooks/PharoByExampleTwo-Eng
• publish the changes and notify the list.

See PBE-TO-DO.txt for status of tasks for PBE 2.

# File structure

The main file is PBE1.tex. Chapters are in subdirectories. You can latex either the entire book, or each individual chapter. Each chapter file starts and ends with the same incantation which will optionally include macros or end the document if it is latexed individually.

Use the \ct{} macro for in-line code. Use the {method}, {classdef}, {example} and {script} environments for multi-line code.

If you add a new chapter:

• please be sure to include it from PBE1.tex.
• Remember to include its /figures/ subdirectory in the graphicspath, which is set in the preamble to PBE1.tex. Don't forget the trailing /
• Please make sure the chapter compiles with latex both from the main book and as a separate chapter.
• Set the svn:ignore property on the chapter's directory. The command to do this is svn propset svn:ignore -F .svnignore <directory name>

IMPORTANT: Please check out a fresh copy of the book and compile the book to verify that you have added all the dependent files (e.g., figures).

## Makefile

To build the PDF of the book, simply run make in the Book folder. Be sure you have texlive installed (see below).

## Printing

The book has been reformatted to 6"x9" (for Lulu). If you want to print any part of the book, you will find that printing 2 up at 140% works well.

# Testing

Tests are automatically generated from the LaTeX sources.

Grab a recent Pharo image and move it to the folder Pharo book folder. Do not use a 1-click image, since the actual image should be located at the same level as the PBE1.tex file.

To run the tests, load the package PBE-Testing from the following SqueakSource project:

MCHttpRepository
location: 'http://www.squeaksource.com/PharoByExample'
user: ''


Then evaluate the following expression in a workspace:

PBEmain new runTests


PBE2main new runTests


This will automatically extract and run the tests in the LaTeX sources of the Pharo by Example book. It will also load the hands-on exercises, and check that they are working. (Some tests may also be included from the dependent hands-on packages.)

This will parse (using Regex) the PBE1.tex (resp. PBE2.tex) to locate the included chapter files, parse each chapter file to search for @TEST annotations, generate test case classes for each chapter with tests in a new category PBE-GeneratedTests, and generate a test method (numbered by the line number in the chapter) for each test found. (NB: Any old generated tests are removed before new ones are generated.) Finally, by sending "runTests", a TestRunner is opened on the new category, and all those tests are run.

## How to write tests in LaTeX

A sample test in the BasicClasses looks like this:

=\begin{code}{@TEST}
=a1 := { { 'harry' } } .
=a2 := a1 shallowCopy.
=(a1 at: 1) at: 1 put: 'sally'.
=(a2 at: 1) at: 1 --> 'sally'
=\end{code}


The "print it" invocation (-->) will generate an assertion.

The generated source code looks like this:

=test204
=   a1 := { { 'harry' } } .
=   a2 := a1 shallowCopy.
=   (a1 at: 1) at: 1 put: 'sally'.
=   self assert: [ (a2 at: 1) at: 1  ] value printString = '''sally'''


You may also silently declare or initialize variables immediately after @TEST, and you may now place comments after the test string:

=\begin{code}{@TEST |a b|}
=a := b := 'hello'.
=a == b --> true "two variables but one object"
=\end{code}


The generated testCase subclass is PBEBasicClassesTestCase.

The generated tests can be removed by evaluating "PBEmain removeOldTestCategory". This is done automatically whenever you do "PBEmain new runTests".

# LaTeX version

Please use at least texlive 2005. http://www.tug.org/texlive/ If you are using TeXshop or another GUI, be sure to set the path to the tex executables. E.g., in TeXShop>Preferences>Engine set the path to: /usr/local/texlive/2005/bin/powerpc-darwin

For intel macs you will need texlive 2007. The path should be /usr/local/texlive/2007/bin/i386-darwin

## OmniGraffle files

Please be sure to use Lucida Sans, not Helvetica, or you may have problems uploading the PDF to Lulu. See the font embedding FAQ on lulu.com See more detailed instructions in Cover/README.txt

## Style files

To inform latex about the location of local style files, set the following environment variable (tcsh):

setenv TEXINPUTS ./local//:../local//:
or (bash):
export TEXINPUTS=./local//:../local//:


If you are using a GUI like TeXshop, you must set the environment variable in ~/.MacOSX/environment.plist :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>TEXINPUTS</key>
<string>./local//:../local//:</string>
</dict>
</plist>


NB: You may need to logout and login again after creating or modifying this file. Note colon at end of TEXINPUTS that means "append current value here" (eg local has higher priority). Double slash means search recursively.

# Bibliography

The bibliography file scg.bib is available from a separate git repository:

git clone git@scg.unibe.ch:scgbib


Alternatively, you can check out a read-only version as follows:

git clone git://scg.unibe.ch/scgbib


You should separately check out this file and link it in wherever it is needed.