I am trying to test DSM, but it does not work on Namespaces, and thus
on Java models this will lead to a crash.
Would it be possible to fix it in the next couple of days? If not, we
need to make the menu items work only with PackageGroup.
Also, I tried them on a Smalltalk system, but they are just too many
and with only very little differences between them. It would be great
to trim them before the release.
"What we can governs what we wish."
Hi scg members
do not forget that we will have fun at your place.
Please register so that we know how much we should buy.
> From: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Date: February 20, 2010 10:32:18 AM GMT+01:00
> To: Pharo-project Development <Pharo-project(a)lists.gforge.inria.fr>
> Subject: [Pharo-project] Sprint at Bern
> Reply-To: Pharo-project(a)lists.gforge.inria.fr
> Hi guys
> the software composition group of the university of bern is organizing a Pharo sprint
> saturday 13 of march.
> You are all welcome.
> Thanks SCG for organizing and hosting this.
> Stef (we should blog about it)
> Pharo-project mailing list
As you might know, Lukas has created a very nice framework for
building parsers called PetitParser.
This would come as a very nice addition to Moose as it would cover the
weak point of dealing with unknown languages. Thus, I would like to
include it in the default configuration and in the 4.0 release.
I already used it with success in a client project, it comes with many
tests (all green) and it does not conflict with anything in Moose.
Please let me know if you have any objections.
I already created a minimal Moose page with loading instructions:
"One cannot do more than one can do."
The following screenshot shows two bugs:
- Falws , where I guess it should flaws
- selecting a model does not shows up the list of groups associated
to it ("all famix classes", ...)
I just loaded the very last version of Moose
Alexandre Bergel http://www.bergel.eu
Moose Suite 4.0 beta 5 is now available for download:
The same version can also be loaded into a Pharo Development image by
executing the following code:
((Smalltalk at: #ConfigurationOfMoose)
project version: '4.0-beta.5') load.
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
I'm trying to convert some packages from VW to Pharo. For that, I use the
technic described in the SCG wiki (using the squeak exporter in visual works
and then dragging the .st file in pharo). For some packages it works well.
For other, I have syntax errors (that don't really described the problem).
In these case, what is the solution ?