Hi,
The reason was to allow people to remove caches in one shot without removing basic properties. I used them a lot during development of traversals and queries.
However, we can probably remove them now and favor fast loading of a whole model instead.
Cheers, Doru
On Sep 24, 2017, at 10:56 AM, Cyril Ferlicot D. cyril.ferlicot@gmail.com wrote:
Le 24/09/2017 à 09:06, Stéphane Ducasse a écrit :
I do not get why you get then a so large image of 260 Mo? The default Pharo moose image fully charged with a model with 120000 classes that I created from undertsand is 93 Mo There is something strange.
I'll open an issue on our bug tracker to check this.
There are probably two dictionary so that you can show only properties in the tools. and you do not need to know what are the cached queries so if you merge the two then it means that you should keep a way to distinguish between queries and others.
I think this is not the reason because then you cannot display properties that are not in cache if you just take the properties of the MooseDefaultState.
In anycase if it is something like this then I can introduce a new state since we do not care of what is a property and what is a query in the tools. We have our own layer in top of FAMIX.
Now about the properties may be we should encode them differently. I’m writing an email about how to reuse metrics computation and I will send it.
Ok
Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France
-- Cyril Ferlicot https://ferlicot.fr
http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com
“Software has no shape. Actually, it has no one shape. It has many."