Le 23/09/2017 à 21:01, Stéphane Ducasse a écrit :
I was thinking more about Moose, Seaside….. Because Pharo is not that large. Even if we can remove things. And the bootstrap is not really related to that.
From Moose we get only FAME and FAMIX, but we can restrict a little more FAMIX. I would like to make groups depending of the language because for now we load everything for every language. Not loading the Smalltalk package into non smalltalk technologies would help us to reduce the time of queries.
For Seaside I opened an issue on Seaside issue tracker some weeks ago to be able to load seaside without the tests. It will probably be done for Seaside 3.3.
Then I think we use pretty much everything that we load on top of Pharo.
ok do you know when the queries dict is used? Because this is the first time I hear about it.
Here is the list of usages I see:
- MooseModel use it to save bookmarks - FAMIXContainerEntity use it in #classes - FAMIXNamespace use it for #methods - FAMIXPackage use it for #classes, #concernedClassesCollection, #extendedClasses, #extensionClasses, #extensionMethods, #localMethods - Other FAMIXXXX use it that way - MooseAbstractGroup use it in the #allModelXXX methods and #allWithSubTypesOf: …
Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org%C2%A0 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
On 23-09-17 21:54, Cyril Ferlicot D. wrote:
For Seaside I opened an issue on Seaside issue tracker some weeks ago to be able to load seaside without the tests. It will probably be done for Seaside 3.3. Then I think we use pretty much everything that we load on top of Pharo.
Is there an issue with that? AFAIK we were always able to load Seaside without tests. I can't find an open issue
Stephan
Le 23/09/2017 à 22:35, stephan a écrit :
Is there an issue with that? AFAIK we were always able to load Seaside without tests. I can't find an open issue
The issue is already closed :
https://github.com/SeasideSt/Seaside/issues/942
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
On 23 Sep 2017, at 21:54, Cyril Ferlicot D. cyril.ferlicot@gmail.com wrote:
Le 23/09/2017 à 21:01, Stéphane Ducasse a écrit :
I was thinking more about Moose, Seaside….. Because Pharo is not that large. Even if we can remove things. And the bootstrap is not really related to that.
From Moose we get only FAME and FAMIX, but we can restrict a little more FAMIX. I would like to make groups depending of the language because for now we load everything for every language. Not loading the Smalltalk package into non smalltalk technologies would help us to reduce the time of queries.
Indeed.
For Seaside I opened an issue on Seaside issue tracker some weeks ago to be able to load seaside without the tests. It will probably be done for Seaside 3.3.
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.
Then I think we use pretty much everything that we load on top of Pharo.
ok do you know when the queries dict is used? Because this is the first time I hear about it.
Here is the list of usages I see:
- MooseModel use it to save bookmarks
- FAMIXContainerEntity use it in #classes
- FAMIXNamespace use it for #methods
- FAMIXPackage use it for #classes, #concernedClassesCollection,
#extendedClasses, #extensionClasses, #extensionMethods, #localMethods
- Other FAMIXXXX use it that way
- MooseAbstractGroup use it in the #allModelXXX methods and
#allWithSubTypesOf: …
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.
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.
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 https://ferlicot.fr/
http://www.synectique.eu http://www.synectique.eu/ 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France
-------------------------------------------- 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
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%C2%A0 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
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."
Le 24/09/2017 à 11:54, Tudor Girba a écrit :
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
So I can create a MooseMemoryEfficientState that will be used by default and then rename MooseDefaultState into MooseDevelopmentState. Then we could let an option in the model to switch to the state we want.
If everyone agree I'll do the change.
Thank you for the infos.
-- www.tudorgirba.com www.feenk.com
“Software has no shape. Actually, it has no one shape. It has many."
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev