Pharo, the programming language, live IDE and core library has a new release!
The past year seemed short as we got busy building more than usual. Many things have changed in Pharo. Here are the highlights:
- The new modular Opal compiler is now the default compiler used in the system.
- The Athens vector graphics canvas is now integrated and it supports Cairo rendering on all platforms.
- Many tools have been rewritten using Spec, a new framework for building user interfaces.
- Versionner and Kommiter are two of the new development tools.
- RPackage, a new package mechanism got enhanced with tags and is fully integrated in the system.
- The debugger model was rewritten to become modular, the inspector received a bump to support multiple views, and the Nautilus code browser supports tags, search and lot more improvements.
- Morphic has seen many cleanings and improvements and the visual theme has been revamped.
These are just the more prominent highlights, but the details are just as important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues in Pharo 2). Take a moment to go through a more detailed recount of the progress: ChangeLogs 3.0.
Pharo is improving on many fronts. Just take a look at the code city of Pharo (built with Pharo for Pharo). Every building is a class, and the red bricks represent the modified methods in Pharo 3.0.
Many things are changing but the system gets more stable. Moving from Pharo 2 to Pharo 3 is almost a matter of just loading the code.
Remember that Pharo is your platform. We thank all the contributors of this release: JeanBaptiste Arnaud, Simon Allier, Philippe Back, Clément Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa Peña, Nicolas Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Sergi Reyner, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan Wilkinson.
And many many more who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback...
Pharo 3.0 is the largest step we took since we started. Yet, it’s just a step. Expect more. Much more.
The Pharo Team
Richard Wettel just announced that a new implementation of CodeCity is available on top of the latest Pharo and Moose.
CodeCity is a 3D visualization engineased on a city metaphor, which enables us to depict software systems as cities. If you want to know more about this approach, have a look here: http://www.inf.usi.ch/phd/wettel/codecity.html.
For example, here is a city of ArgoUML 0.34:
To install CodeCity, you need to run this code in a Moose image:
smalltalkhubUser: 'RichardWettel' project: 'CodeCity';
(Smalltalk at: #ConfigurationOfCodeCity) loadDevelopment
You can also get the latest successful build from: http://ci.inria.fr/moose/job/codecity/lastSuccessfulBuild/artifact/codecity.zip
The new CodeCity does not provide a configuration UI, but it relies on scripting. A script to obtain a city visualization of a Moose model is shown here:
A good way to get familiar with the scripting API of CodeCity are the examples. You can open CCBuilder in the Playground and you can browse the examples (the "e.g." tab).
While CodeCity was initially aimed at software systems only, there is nothing that stops you to use it now for visualizing any kind of data!
A new post on the humane assessment blog describes what makes makes Moose unique in its focus of helping developers craft custom analyses.
The post covers the central idea and some of the more prominent engines (PetitParser, Fame, Glamour and Roassal) and describes how they all come together in the Finder interface.