Skip to content

pharo

How does Monticello merge?

There is a repeated confusion on how merging in Monticello works. This post tries to clear up the situation. In the following examples we always start from the same situation displayed below. P is the name of the package we are working with and the number behind P.1 signifies a specific version of that package. The Working Copy is the code we currently have in our Smalltalk image.

Disk Filesystem

A while ago Colin Putney announced the Filesystem framework, a nice and extensible replacement for the ugly FileDirectory class in Pharo. While all core classes are well commented, there is a quick start missing that explains how end users are supposed to adopt the framework. This blog post should fill that gap.

Pharo by Example

The open-source book Pharo by Example has been announced. It is a new, improved and adapted version of Squeak by Example to Pharo, the new Smalltalk that is quickly approaching its 1.0 release. One of the particularly exciting additions to the book is the chapter Seaside by Example.