Hello,
I asked a question on Discord bug I got no answer. Maybe I will have
more arswer here.
The moose state has three different caches:
- attributes
- property cache
- query cache
I know that the attribute cache is a cache that is rarely cleared. But
what is the difference between the propertyCache and the queryCache?
Could we not just use the propertyCache all the time?
--
Cyril Ferlicot
https://ferlicot.frhttp://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France
Hi,
You should ask in the Moose list ;)
Vincent
> -----Message d'origine-----
> De : Alidra Abdelghani [mailto:alidrandco@yahoo.fr]
> Envoyé : mercredi 7 juin 2017 15:34
> À : pharo-users(a)lists.pharo.org
> Objet : dynamic interaction with Mondriam
>
> Hi all,
>
> I would like to do some visualisations with Mondrian where you change the
> visualisation by selecting actions. For instance you have :
> b := RTMondrian new.
> b shape rectangle withTextAbove.
> b nodes:(1 to: 5).
> b layout grid.
> b edges connectFrom: [ :e | e + 1 ].
> b build.
> b view
>
> then you can click a button to:
> 1 display/hide the labels above the elements.
> 2 display/hide some elements (all odd numbers for instance)
> 3 display/hide connections between elements.
> I saw a visualisation in the Roassal examples where you can add elements in a
> dynamic stack grapher. So I presume it is possible to do the same with other
> types of visus.
>
> Any hints?
> Thanks in advance.
> Abdelghani
!!!*************************************************************************************
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Hi,
Take a look at this script:
http://ws.stfx.eu/54G9IO1XX4R2
It produces this. The issue is that instead of aligning the top left, it kind of centers the entities from the same layer:
This used to work properly, and the tree algorithm did not change. So something must have changed not too long ago related to translations. Does anyone have a better idea of where this could come from?
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"From an abstract enough point of view, any two things are similar."
Hi,
Now that Pharo 6.0 was released, I want to prepare for the Moose 6.1 release.
I went through most of the issues and closed half of them. We still have some 78 total issues open. I marked some that I find important for the release here:
https://github.com/moosetechnology/Moose/milestone/2
Please take a look at the issue tracker and feel free to add the 6.1 milestone to them.
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"What is more important: To be happy, or to make happy?"
Hi,
An intern of the RMod research team needs your help:
Cheers,
Vincent
De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Benoit Verhaeghe
Envoyé : mercredi 7 juin 2017 16:47
À : pharo-users(a)lists.pharo.org
Objet : [Pharo-users] Need help for collecting tests usage data
Hi everyone.
I need your help. I’m working on how pharo developers use the tests. And you are pharo developers.
So I developed a plugin and I would like you to download it. You just have to execute this line in a playground
Metacello new
smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo60';
configuration: 'TestsUsageAnalyser';
version: #stable;
get;
load.
You will have to do it only one time in one image. Then, if they are updates it’ll be done automatically and if you create a new image it will be automatically installed.
The plugin will collect data on which tests you run, when, and the modifications you'll have done.
Normally, it should be completely transparent for the users and the data are anonymous.
If you want more details about the project or how it works, you can answer to this mail, or send me an email at benoit.verhaeghe(a)inria.fr<mailto:benoit.verhaeghe@inria.fr> or by using discord.
Thanks a lot.
Benoit Verhaeghe
!!!*************************************************************************************
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Dear World,
The time has come for Pharo 6.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
This is our most significant release yet. Here are some highlights:
- Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing)
- A new code changes management system named Epicea for easier reviewing and recovering of your code easily
- Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7)
- The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved
- The PharoVM is now part of OpenSmalltalk initiative
- Introduction of object immutability, alternative bytecode sets and block closures independent of outer context
- Pharo can now be bootstrapped from source code managed by Git
- Pharo modularity is improved
- Pharo is faster
- The Dark Theme was improved and set as default color theme of Pharo
These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…>).
While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk
(If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy!
The Pharo Team
Try Pharo: http://pharo.org/download <http://pharo.org/download>
Learn Pharo: http://pharo.org/documentation <http://pharo.org/documentation>
Hello everyone,
I would like to talk about something I would love to see in Moose: a
Mock framework.
I love to have a stable structure so I love tests. But sometimes it is
hard to produce tests for Famix because the models are complex and I
want to test a specific, simple, case. I think that as a code quality
analysis platform, Moose *needs* to get a Mock framework.
Thus I would like to add Mocketry to the dependencies of Famix or Fame.
Why Mocketry? Because we already have some of its dependencies in the
dependencies of Famix and because I find it easier to use than BabyMock.
So... Do someone has objections? Do someone think we need a Mock
framework but thinks that Mocketry is not the right one?
If I have no objection I'll add the dependency then some more tests :)
--
Cyril Ferlicot
https://ferlicot.frhttp://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France
