As ESUG was so inspiring, I could not resist some VW hacking on the
If you browse to WideClass and WideClassTest on SCG Store, there is a
simple implementation of wide classes. As we have tons of empty inst
vars in moose models, that might help us to save some megas on large
How to use it?
Sending #wide:put: to any object will install an instance var and
accessors on the receiver instance.
o := Object new.
o wide: #foo put: 4.
and even better, if you implement #foo and #foo: as follows
foo: arg self wide: #foo put: arg
upon first execution of #foo: the foo inst var is installed and both
methods get properly overriden with simple accessors. There is no DNU
Hope you have some fun playing around with it!
As I mentioned during the moose workshop we would like to get your
evaluation of our ideas.
I would really like if you could perform the experiment described at:
Today I tried to import from mse files and I get the following
exception during the import:
"Message not understood: #accessedByLists"
Then, I tried to import a model from Smalltalk and to export it in
mse. Loading this fresh file generated the same exception. Could you
please fix this?
(I peeked a bit in the Moose code and it seems that
FAMIXAbstractStructuralEntity has an accessedByList attribute and two
pairs of accessors: #accessedByList and #accessedByLists and the
setters, too. Maybe it has something to do with this).
Thanks and cheers!
PS. And another issue is that when I tried to load the latest
MooseDevelopment bundle, I got some packages that could not be loaded...
I chatted with Travis Griggs and he showed me a package called
LessProgress. This packages replaces the ugly progress bars that
always get on top of any window with a small progress bar in the
Launcher (see attached picture).
To use it, you have to:
- load LessProgress (either from Cincom or from Bern Store)
- go to the Window menu in the Launcher
- New Launcher
I put this in my base image.
"We cannot reach the flow of things unless we let go."
Dear Moose und Famix Community,
the founding assembly of the Moose Association will take place at
ESUG on August 30, 2007 in Lugano, Switzerland. The assembly will
start after the last presentation of the ESUG conference, that is
after 18:00. The conference rooms are located in the top floor of the
red building of the Università della Svizzera italiana. Please refer
to the link below for directions
Below the Trakdandenliste (agenda) and a link to the bylaws
- Election of founding president and keeper of minutes
- Put on record the names of all participants
- Discussion about purpose and focus of the association
- Discussion and approval of the bylaws
- Discussion about and election of advisory board
- Election of the executive board
http://moose.unibe.ch/association/bylaws (in German)
The founding assembly will be held in English.
For more information please refer to http://moose.unibe.ch/association
in the name of the Moose team,
Adrian Kuhn MSc
Software Composition Group
as you might remember, the founding of Moose Verein was postponed at
Famoosr due to missing bylaws. The purpose of the association is to
support Moose and Famix, eg by organizing a Summer of Code.
We plan to found the Moose Verein at ESUG in Lugano, see doodle
I have setup a wiki page with draft bylaws, taken from the nice
booklet "Wie gründe und leite ich einen Verein?" by Urs Scherrer. See
The bylaws are in German. It would be nice if someone could translate
them to English. The English bylaws will not be legally binding, they
are only meant as support for foreign-speaking members. The google
translation looks 90% correct, hence the translation job would mainly
be to fix mistakes like "photograph request" for "Aufnahmegesuch".
@Orla, you said that you might volunteer for translation, is that
still okay with you?
Please stay tuned for more news, and forward this mail to anyone in
your network that might have an interest in the Moose association.
Adrian Kuhn MSc
Software Composition Group
I saw you added the Ecore code into Meta. I did not have the time to
take a closer look, but I did noticed you have a lot of tests for
your code, and they are all green. That is nice :).
As you probably saw in the previous mail, adding EcoreImportExport to
Meta generated some loading problems when loading 'Moose Config',
because you have two classes that are in SCG.Moose namespace.
However, Meta does not depend on Moose, but Moose depends on Meta.
So, no class in the Meta bundle should be in the Moose namespace.
I see several solutions to fix the problem:
- move the classes to the Meta namespace for now, although they do
not belong there
- move the classes to the MooseDevelopment bundle
- move the classes in a separate bundle that has MooseDevelopment
bundle as prerequisite
Also, please add comments to the versions you are adding, because it
helps us track what is happening.
In any case, I am looking forward to taking a closer look at the
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
the issue is fixed, now you can say
SCG.Moose asMetaDescription classes
and get all meta-descriptions of all classes without the annoying
PS: next week I am in Berlin, I might not have time to fix bugs, but
I am usually available via mail.
On 27 Jul 2007, at 15:32 , sellossa(a)ensieta.fr wrote:
> why, when I do: SCG.Moose asMetaDescription, I get sthing different
> from when I do: SCG.Moose allClasses do: #asMetaDescription.
> ^SCG.Moose asMetaDescription
> Stef find it terrible!