[Ann] Iceberg V1.1.1

Hi everybody,

This week we have a small patch release of Iceberg, version v1.1.1.
This version will be available in the next Pharo build.

In summary, this release fixes two issues with the new credentials manager,
and introduces a couple of other enhancements/bugfixes.

Below you will find the detailed changes log.

Integrate Iceberg 1.1.1


#864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing
repositories lead to wrong source directory
#861 <https://github.com/pharo-project/pharo/pull/861> update tonel to
#836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType
class variable is unused
#862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are
not running in Pharo 7
#852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs
#858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph
does not allow select and copy anymore
#850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head
status from error to warning if we are on a tag
#853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog
"username" is confusing
#860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API
#854 <https://github.com/pharo-project/pharo/pull/854> Error in History

Collecting sensor data with PharoThings


On this page you can see the temperature, humidity and pressure data of my room in Inria, in real time (or almost real, 10 min between the data …)

Allex Oliveira

Screen Shot 2018-06-18 at 14.03.53.png

News from PharoThings

The first words of PharoThings on LCD HD44780.

The breadboard is to better organize the components. It’s easier manipulate the wires using it.

In that breadborad, I has 3 sensors (MCP9808, BME280, ADXL345), 2 leds, 2 buttons and 1 LCD. The potentiometer is to control the energy power to LCD.
More volts is more contrast on LCD.
Allex Oliviera


1500 pull requests closed :)


As of today, we closed 1500 pull requests:

https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls>

These of course range from trivialities to merging sub-systems with hundreds of commits…


[Ann] Gt Documenter


We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment:

Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka.

Attached you can see a preview of how documents look like:

At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases:
	• code documentation
	• tutorials
	• interactive data notebook

Code documentation
Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation:

You can see a live example of documentation by inspecting the following snippet:
	GtDocumenter editorForText: BrToggleExamples comment. 

Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation:

The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview.

The size of the preview can also be adjusted live:

You can see a live tutorial by inspecting:
	IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar’.

Interactive data notebook:
A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground:
	• it supports defining variables in code snippets, and
	• the execution of code shows an embedded inspector.

For example:

An example, can be seen by inspecting:
	IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. 

As always, please do let us know what you think.

The feenk team

[Ann] Iceberg 1.1.0

Time for the weekly Iceberg update.
Thanks to all brave users, issue reporters and contributors :).

Key changes: we have introduced some tag support, a new credential manager to manage keys and passwords per host or repository, a new version of tonel, and made a first step towards a simplified contribution to Iceberg by listing it as Pharo's repository.

Guille in behalf of all Iceberg contributors

Following, the detailed changes log.

New Features
#842 <https://github.com/pharo-project/pharo/pull/842> Adding Credentials
#843 <https://github.com/pharo-project/pharo/pull/843> Update Tonel to 1.0.7
#823 <https://github.com/pharo-project/pharo/pull/823> Iceberg repository
should be listed as Pharo's one
#841 <https://github.com/pharo-project/pharo/pull/841> Basic tag support (
#372 <https://github.com/pharo-project/pharo/pull/372>)

#787 <https://github.com/pharo-project/pharo/pull/787> Add Windows ci with
Appveyor (not yet green!)

#827 <https://github.com/pharo-project/pharo/pull/827> Add package dialog
has some glitches
#833 <https://github.com/pharo-project/pharo/pull/833> replace #asIcon with
#832 <https://github.com/pharo-project/pharo/pull/832> Move Iceberg from
MostUsedTools to Tools
#830 <https://github.com/pharo-project/pharo/pull/830> Better handling of
not github remote urls
#825 <https://github.com/pharo-project/pharo/pull/825> Enhance Migrate to
tonel commit message
#637 <https://github.com/pharo-project/pharo/pull/637> Show tag version
instead of "Detached HEAD"
#829 <https://github.com/pharo-project/pharo/pull/829>

Bug Fixes
#835 <https://github.com/pharo-project/pharo/pull/835> Compare file
definitions by their binary uninterpreted content
#838 <https://github.com/pharo-project/pharo/pull/838> Clone from incorrect
github repository fails with DNU
#826 <https://github.com/pharo-project/pharo/pull/826> Pushing to virgin
repository raises a DNU


Pharo Shop



Thanks Lusy for the design.

Pharo being shown at main ICSE research track!

Great job! Juraj, Alex and others.

We have the answer to the first questions! Yes live programming is useful for real projects!