Last updated at 9:29 am UTC on 17 April 2017
Pharo is a fork of Squeak.
The first release was in April 15, 2010.
Pharo by example
Classic Morphic code is still mostly compatible with Pharo. Pharo uses a different ToolBuilder system for the tools, more see http://gtoolkit.org/.
It contains a new text model TxModel (Pharo).
Many Pharo projects are hosted on Smalltalk hub.
List of all projects: http://smalltalkhub.com/list
Roassal is visualization engine written for Pharo Smalltalk.
In Pharo a versioning system called Iceberg may be used. It is an abstraction over a distributed source code versioning system looking like git.
Pharo collaborative active book
<email@example.com> Sun, Apr 16, 2017 at 4:42 PM
Reply-To: Pharo Development List <firstname.lastname@example.org>
To: Pharo Development List <email@example.com>
A historical perspective...
Prior to this coming Release 6, Pharo had diverged from the parent build system
used by OpenSmalltalk (nee Squeak-VM) such that (IIUC) it was driven from the
Image generating the generated-C-sources plus the Cmake configuration.
I guess this is what you describe as "bootstrap".
However for Release 6 onwards, Pharo has returned to the fold and is directly using
the OpenSmalltalk build system. The OpenSmalltalk build system does not require
a build to invoke a Smalltalk image, and I notice elsewhere you've seen the ./mvm script.
Eliot currently manually updates the checked-in generated-C-sources at times he
considers them stably generated from VMMaker-Image, although I think I saw
recently some mention of doing CI on each VMMaker check-in..
So the Pharo 5 in-Image CMake generation system is deprecated, and
I guess there will not be much further development on the Pharo 5 VM.
More see DocumentationForCOG