We are very happy to make the following announcement:
Lam Research, a leading supplier of wafer fabrication equipment and services to the global semiconductor industry, is an experienced user of the Smalltalk programming language. Smalltalk is a key component in Lam's software control system for a broad range of the equipment it manufactures. Tudor Girba is a leading member of the tools and environment development effort in Pharo, having architected the Glamorous Toolkit for live programming. Eliot Miranda is author of the Cog virtual machine that underlies Pharo and other Smalltalk dialects.
Lam has engaged Tudor and Eliot to explore potential enhancements in Lam's use of Smalltalk. These enhancements range from running highly optimized Smalltalk on low cost, single board computers, to enhancing Lam's Smalltalk development practices with state-of-the-art live programming. During the engagement, Tudor and Eliot successfully moved a key communication component of the control system to Pharo. It was a challenging task aimed at extending the reach of Lam’s system to the Pharo world including the option of executing on ARM processors.
Cheers,
Tudor Girba, Eliot Miranda and Chris Thorgrimsson
We are happy to announce version 6.0 of the Moose Suite, the platform for software and data analysis built in Pharo:
http://moosetechnology.org/#install
Description
The key highlights are:
- It is based on Pharo 5.0 including the latest version of the Glamorous Toolkit.
- It includes the SmaCC parsing framework together with parsers and abstract syntax trees for Java, JavaScript and Swift.
- Roassal2 comes with several enhancements.
- Famix features a new and generic query API engine.
- Moose Finder and GTInspector come with more custom presentations and visualizations.
- SmaCC comes with a dedicated debugger.
- The debuggers for Glamour, PetitParser and Announcements received a new update.
- DeepTraverser is an order of magnitude faster.
Extra highlights:
Installation
The Moose Suite 6.0 comes for each platform as a separate bundle:
The Moose Suite 6.0 can also be loaded in a Pharo 5.0 image either from the Configuration Browser, or by executing the following script:
Metacello new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration: 'Moose';
version: #stable;
load.
Enjoy,
The Moose team
Over the last couple of weeks I worked on a new importer for Java code that can be used for Moose, and I am happy to announce that I released version 1.0.1.
jdt2famix is an open-source project, and the repository can be on Github. It is implemented in Java as a standalone project, and it is based on JDT Core (developed as part of the Eclipse project and available under the EPL2 license) and Fame for Java (originally developed by Adrian Kuhn and is available under the LGPL license).
The current implementation has an extensive coverage of entities that it can import, namely:
- classes, parameterizable classes, parameterized types, enums, anonymous classes, inner classes
- annotation types, annotation type attributes
- annotation instances, annotation instance attributes
- methods, constructors, class initializers
- parameters, local variables
- attributes, enum values
- accesses
- invocations, constructor invocations, class instantiations
- thrown exceptions, caught exceptions, declared exceptions
- comments associated with named entities
- source anchors for named entities
The simplest way to use it is through the command line:
- Download and unzip the self contained binary 1.0.1 release.
- Go to the root folder where you have the sources and dependency libraries of a Java system (e.g.,
mysystem) - Execute
/path/to/jdt2famix.sh
The result will be an MSE file having the same name as the name of the folder from which you executed the command (e.g., mysystem.mse).
Let’s look at a concrete example. For this purpose, we pick the Maven project. We first download the 3.3.9 sources. These are only the plain sources, but to be able to import the complete model, we also need to have the dependencies available in the same folder.
As Maven is a Maven project (no pun intended), we can use the configuration to download the dependencies locally:
mvn dependency:copy-dependencies -DoutputDirectory=dependencies -DoverWriteSnapshots=true -DoverWriteReleases=false
(If you do not have a Maven project, you have to adapt this step and obtain the dependencies depending on the specifics of your project)
Then we simply execute:
/path/to/jdt2famix.sh
And we get a maven-3.3.9.mse file that we can load into Moose.
