Pharo by Example (vol 1) is a practical introduction for Pharo, a Smalltalk-inspired programming language, IDE and live coding enviroment. This book is an updated version of Pharo By Example for Pharo 1.4.
This version focuses on the latest stable version of Pharo (Pharo 4, at the time of writing).
You can find more info and documentation about Pharo at Pharo.org.
|1 - Preface||Revised, copyedited||html pdf|
|2 - Pharo Tour||Revised, copyedited||html pdf||
|3 - A First Application||Copyedited, Needs revision||html pdf||
|4- Syntax in a Nutshell||Revised, copyedited||html pdf||
|5 - Understanding Messages||Revised, copyedited||html pdf||
|6 - The Pharo Object Model||Needs revision||html pdf||
|7 - Environment||Copyedited, Needs revision||html pdf||
|8 - Sharing Code and Source Control||Copyedited, Needs revision||html pdf||
|9 - SUnit||Revised, copyedited||html pdf||
|10 - Basic Classes||Revised, copyedited||html pdf||
|11 - Collections||Needs revision||html pdf||
|12 - Streams||Revised||html pdf||
|13 - Morphic||Needs revision||html pdf||
|14 - Seaside By Example||Needs revision||html pdf||
|15 - Classes and Metaclasses||Revised||html pdf||
|16 - Reflection||Needs revision||html pdf||
|17 - Regular Expressions in Pharo||Needs revision||html pdf||
Contributing to Updated Pharo By Example (vol 1)
This book follows the fork-and-pull GitHub workflow for contributions:
- Fork the repository
- For each addition, create a quick branch, prefixed with your initials. For
git checkout -b dz_streams_syntax_fix
- Make commits to that branch. When you're ready, make a Pull Request
- The request will receive comments/corrections, and will be merged into the main repo.
More info about contributing to this book (including Pillar syntax, setting up LaTeX, etc) can be found in the CONTRIBUTING.md file.
Reference Links to Other Chapters
Whenever you refer to other chapters of the book, please use the Pillar internal
link syntax and the chapter name. (The
cha: in the id is to denote that it's
a chapter, to differentiate from a section id.) For example:
Chapter *cha:tour*: A Quick Tour of Pharo
A list of chapter ref link code is provided, to easily copy and paste, in the Chapter Progress / table of contents above.
Please keep in mind the following:
- When possible, hard-wrap lines at 80 characters (e.g.
Cmd-Alt-Qin Atom). This is a common open-source documentation convention, and helps with viewing GitHub-generated diffs. However, due to Pillar limitations, ordered and unordered list elements must be on a single line to be correctly parsed. Those can be left un-wrapped.
- Only one space between sentences.
- Avoid periods in section titles. (For example, this section is titled "Style Guide" and not "Style Guide.")
- All inline code mentions (objects, messages, variables, packages) should use the
Pillar monospace notation:
The latest versions of Updated Pharo by Example can be found at the following sites:
- Jenkins Latest PDF: UpdatedPharoByExample.pdf. All Chapters: UpdatedPharoByExample build artifacts
- Travis (https://travis-ci.org/SquareBracketAssociates/UpdatedPharoByExample)