Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

Need help for collecting tests usage data

by Blondeau Vincent

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.!!!"

7 years, 7 months

[ANN] Pharo 6.0 released!

by Tudor Girba

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>

7 years, 7 months

Integrating Mocketry

by Cyril Ferlicot D.

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.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

7 years, 7 months

Roassal @ Pharo TechTalk

by Alexandre Bergel

Hello, Tomorrow Roassal will be the topic of the month Pharo TechTalk. When: TechTalk Voice channel @ Discord, Youtube channel When: 4:00 PM (GMT+2, Paris Time), 11:00 (GMT-3, Argentina time) 10:00 AM (GMT-4, Chile time), 7:00 AM (PDT, San Francisco) Length: about 30 minutes How to join: - Youtube Channel for the video: https://www.youtube.com/watch?v=hmnDGbM5vsY - Discord for the sound: http://discord.gg/Sj2rhxn Website of Pharo TechTalk: https://association.pharo.org/event-2489995 Content of the Roassal TechTalk: 1 - General introduction of Roassal 2 - Latest news in Roassal (Theme support, Scatterplot Matrix, Elastic boxes, ...) 4 - Applications based on Roassal (Test Coverage, Memory profiling) 3 - Ongoing effort and future work The presentation of the TechTalk will be essentially demo-based. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

7 years, 7 months

Re: Moose-dev Digest, Vol 129, Issue 10

by Alidra Abdelghani

Perfect, Thanks a lot Vincent :-) Abdelghani > On 23 May 2017, at 12:00, moose-dev-request(a)list.inf.unibe.ch wrote: > > Date: Mon, 22 May 2017 13:57:53 +0200 > From: Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> > To: Moose-related development <moose-dev(a)list.inf.unibe.ch <mailto:moose-dev@list.inf.unibe.ch>> > Subject: [Moose-dev] Re: unitary tests with moose models > Message-ID: > <55CFA91A8C333946A29A0E4F07F847390110548DB294(a)FRSPX100.fr01.awl.atosorigin.net <mailto:55CFA91A8C333946A29A0E4F07F847390110548DB294@FRSPX100.fr01.awl.atosorigin.net>> > > Content-Type: text/plain; charset="utf-8" > > Hi Abdel, > > You can take a look in the package: Moose-Tests-SmalltalkImporter-LAN > > The Smalltalk code to import some code from the image is : > > model := MooseModel new. > MoosePharoImporterTask new > importerClass: SmalltalkImporter; > model: model; > addFromPackageNamed: #'Moose-TestResources-LAN'; > run; > yourself. > > For the tests, I advise you to put your code sample in a separated package. > > Cheers, > Vincent

7 years, 7 months

unitary tests with moose models

by Alidra Abdelghani

Hi all, I need to test few things on famix entities so I need my tests to load some model. For instance: testSomething aMooseModel := loadModelFrom: somePackage. … what is the easiest way to do so? Thanks in advance Abdelghani

7 years, 7 months

Re: [ann] bloc & cairo+morphic

by Tudor Girba

Hi, It seems that my initial message generated a misunderstanding. My original blog post was meant to communicate two things: 1. That the known Bloc project has received a new feature that the community raised as a problem (i.e., host & backend). 2. Address the other concern that the community raised: how to sustain the Bloc development in terms of engineering effort. This is why we announced the financial support for the work of Alex that is valid from this point on. The post was certainly not intended to overlook the people that contributed to the overall project. I apologize if it looked like this. To clarify the historical perspective, we now added an explicit history page on the official project page: https://github.com/pharo-graphics/Bloc/blob/master/HISTORY.md I also changed the blog post to more clearly communicate the intent: http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ I hope this addresses the concerns. I am really excited that Alain joined and that we can get even more traction around Bloc. Cheers, Doru > On May 12, 2017, at 7:56 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > BTW for an historical perspective > > RMoD me and igor were also involved far less than the effort of alain but as he mentioned it we collaborated on it. I spent time on documenting several versions and I stopped disgusted to see the total lack of attention for comments. > Then Rmod paid nearly a year of effort on Athens, SDL20 support, a year on TxText. I find really strange that we are not even mentioned in any support. > > Stef > > > On Thu, May 11, 2017 at 8:12 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Doru can you change the humane assessment blog post? > > > On Thu, May 11, 2017 at 8:07 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Indeed, this is wonderful news that you will rejoin your baby project :). > > Cheers, > Doru > > > > On May 11, 2017, at 6:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > > Hi Alain! > > > > Thanks for the mail (even if the historial part has always been pretty clear to me). > > We miss you! Be back soon! > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > >> > >> > >> From: Alain Plantec <alain.plantec(a)yahoo.com> > >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > >> Date: May 11, 2017 at 12:36:36 PM GMT-3 > >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > >> Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > >> > >> > >> Hello Doru, all, > >> > >> I’m really happy to see Bloc progresses. > >> Even I’m not active since more than one year, Bloc is still an important project for me. > >> > >> but let me complete this short historical presentation a little bit. > >> > >> Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. > >> The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. > >> Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), > >> I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. > >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the > >> one used together with the layouting system that was implemented by Aliaksel. > >> > >> Please, do not use the humane assessment web site but the github project one instead. > >> > >> I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. > >> > >> Thanks, > >> Cheers > >> > >> Alain > >> > >> > >>> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>> > >>> Hi, > >>> > >>> We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. > >>> > >>> Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. > >>> > >>> <bloc-two-backends-morphic-host-figures.png> > >>> > >>> I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. > >>> > >>> You can find a bit more details about Bloc here: > >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > >>> > >>> Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. > >>> > >>> Cheers, > >>> Doru > >>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> www.feenk.com > >>> > >>> "To lead is not to demand things, it is to make them happen." > >>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > > > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

7 years, 8 months

Re: [Pharo-dev] [Pharo-users] [ann] bloc & cairo+morphic

by Alexandre Bergel

Hi Alain! Thanks for the mail (even if the historial part has always been pretty clear to me). We miss you! Be back soon! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Alain Plantec <alain.plantec(a)yahoo.com> > Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > Date: May 11, 2017 at 12:36:36 PM GMT-3 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hello Doru, all, > > I’m really happy to see Bloc progresses. > Even I’m not active since more than one year, Bloc is still an important project for me. > > but let me complete this short historical presentation a little bit. > > Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. > The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. > Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), > I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. > One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the > one used together with the layouting system that was implemented by Aliaksel. > > Please, do not use the humane assessment web site but the github project one instead. > > I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. > > Thanks, > Cheers > > Alain > > >> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. >> >> Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. >> >> <bloc-two-backends-morphic-host-figures.png> >> >> I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. >> >> You can find a bit more details about Bloc here: >> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ >> >> Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "To lead is not to demand things, it is to make them happen." >> >> >> >> > > > >

7 years, 8 months

[ann] bloc & cairo+morphic

by Tudor Girba

Hi, We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. You can find a bit more details about Bloc here: http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. Cheers, Doru -- www.tudorgirba.com www.feenk.com "To lead is not to demand things, it is to make them happen."

7 years, 8 months

moose & the dark theme

by Tudor Girba

Hi, As you could see, in Pharo we turned the Dark Theme on by default. The question is what should we do with Moose. I think it would be great to have it working with the Dark Theme, but the problem is that the Roassal visualizations do not appropriate in the current theme because of two reasons: - they were conceived on a white canvas - the colors are hardcoded Showing a white canvas in the Dark Theme is not an option. Either we introduce a mechanism to adapt the visualizations to the current theme, or we keep a different theme in Moose than in Pharo. What do you think? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

7 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev