Moose-dev

moose-dev@list.inf.unibe.ch

6624 discussions

by Anne Etien

Hi, We are currently cleaning the traits in FamixNG. Once again, the idea is to remove FamixCompatibility metamodel and to keep only FamixStEntities or FamixJavaEntities (and so on). Obviously, it has incidence on tests. Do you use FamixTypeGroup, FamixClassGroup… and more generally groups in Famix? Thank in advance for your answer. Anne

4 years, 9 months

[ANN] Moose v7.0.0 release

by Cyril Ferlicot

Hello everyone! I'm glad to announce the release of Moose v7.0.0. I'll explain the main changes since Moose 6.1 and what are the future plans for Moose 8 in this mail. * What changed? In this version of Moose a lot of things changed from the meta model management point of view. In Moose 6.1 we only had one big metamodel build with inheritance to analyze all languages. This had a lot of limits and a lot of work has been done to improve Moose on those weak points. In Moose 7, you can now have multiple meta-models independant from each others. This mean that we will now have one meta model by parser. We can also create simple meta-models for test purpose. Also those MM are build by composing stateful traits instead of using inheritance. On top of that we now also have the possibility to use generators to manage meta-models. Instead of writing every classes by hand, we can describe a meta-model in a generator and use it to generate the MM. Then we can use it to regenerate it also. Pavel, who did most of the work, wrote some documentation you can find here: https://pavel-krivanek.github.io/famix/ There is still a lot of work to do to make it better but this will come with Moose 8. The reason we release now is that in Moose 7 we started to have split MM for Java, Pharo, and other languages, but we still have a compatibility meta-model. The work needed to improve Moose further will require to break the compatibility MM. Thus we are releasing a stable version now with a compatibility MM and we will work on a Moose 8 version where the compatibility MM will be removed. * Workflow for bugfixes Another change with Moose 6.1 is that now Moose is managed via Github. This will allow use to do patches or minor releases in case the community find bugs or need some new simple features in Moose 7 as long as it only contains backward compatible changes. * Plan for the next release We already stated to work on Moose 8. We plan to work on multiple aspects: - Improve the usability of the generator, especialy while regenerating MMs - Update the Traits contained in Moose to build our MM. Currently, they are a reproduction of what was in Moose 6.1 in order to get the compatibility model. The goal is to remove all the hacks and get cleaner traits. - Start to build new tools to use the full power of this new version of Moose - Fix bugs that will be discovered after such a big change * How to get Moose 7 You can get Moose 7 in two ways. First is to install it in a Pharo 7 image: ``` Metacello new baseline: 'Moose'; repository: 'github://moosetechnology/Moose:v7.x.x/src'; load. ``` The second is to get it via the Pharo Launcher. It now has a Moose 7 entry to get this version and a Moose 8 entry to get the development version. We will also need to update Moose technology website. * Credits Thank to Pavel Krivanek who did most of the work. Thank also to: - Benoit Verhaeghe - Julien Delplanque - George Ganea - Christopher Fuhrman - Stephane Ducasse - Anne Etien - Nicolas Anquetil - Cyril Ferlicot And any other I might have forgot who participated in the development of Moose 7 :) -- Cyril Ferlicot https://ferlicot.fr

4 years, 9 months

Changes to Metamodel generator

by Cyril Ferlicot

Hi, Last month we did some changes to the MM generator of the development version of Moose and it might impact people using it. I'll explain the changes and what to do in this mail. Context: In the development version of Moose, we have two ways of building a metamodel. The first is to do as in Moose 6.1 and write it by hand. The second and recommended way is to describe it in a MetaModel generator and to generate it. This generator is also able to regenerate a metamodel. In order to do that, it needs to know the Traits and Slots it generated. This was done by generating two methods on each entity: #generatedSlotNames and #generatedTraitNames. Changes: With Julien Delplanque, we updated Moose to remove the need of those two methods. For Traits, we are now able to just ask an entity for its Traits that are part of the metamodel. Thus, we do not need the #generatedTraitNames method. For Slots, we have two kinds. One that describe a relation between entities and another that store properties. The relations already had a slot specific to Famix. We introduced another one call FMProperty to be used to store the properties. With that change, all slots generated by the generator are specific to Famix, thus we can lust ask a class for its famix slots and we do not need to generate a static method with the slot names in entities. Actions to take after this change: We added some compatibility code to keep things working during a transition period. Two actions are needed if you want a clean MM after those changes: - The first one is to remove the #generatedTraitNames methods from the class side of generated entities. - The second one is to regenerate your metamodel and this will automatically replace InstanceVariableSlot by FMProperty and remove #generatedSlotNames methods. Change in generator behavior: This change as a side effect you need to know. Before, regeneration of MM was updating only the Traits and Slots it generated. Now it will regenerate all Traits that are part of the metamodel (with a #MSEClass:super pragma) and all Famix slots. Thus, if you are managing a MM via a generator, you need to update the generator description to add a Trait or Slot from Famix instead of adding it by hand. Else, it will be removed during the next generation. -- Cyril Ferlicot https://ferlicot.fr

4 years, 10 months

Tests for FamixNG

by Anne Etien

Hi everyone, As already explained, we are currently cleaning the traits in FamixNG. Pavel did a great job by providing a back office to create new meta model with a tiny DSL and by building the old meta model using the new infrastructure. Now, we want to: - clean elementary traits (for example when there is a FMMany slot, sometime there is an addXXX method and sometime not) - compose traits (FamixTClass is not a composition of traits, it has to be done when we build the meta model), to provide semantically rich traits. - be sure that tests are passing. They were tests in FamixNG, only to ensure compatibility with the old meta model. Consequently, I developed a generator to create tests associated to elementary traits. Normally you don’t need to use this generator if you use only build traits by composing existing ones. Anyway, if needed, you can get the generator from FamixNG-TestGenerators package in TestGenerator3 branch: fttg := FamixTestAndTraitGenerator new. fttg runFor: FamixTClass I developed a second generator to generate tests from the trait composition. We will use it after cleaning FamixNG. Obviously, later the generator has no vocation to remain in the image, tests will be generated once and you can add tests by hand. fcg := FamixComposingTestTraitsGenerator new. fcg addingTraitsToTestTraitFor: FamixTClass For using this later, we need that a correction in Pharo concerning composition of traits with slots is back tracked in Pharo 7. Or you can use the attached file. We already get 135 tests for FamixNG and we will continue. If you have any question don’t hesitate. Anne

4 years, 10 months

Re: about http://www.moosetechnology.org failing

by George Ganea

It should be up and running now. George > On 25 Jun 2019, at 13:00, moose-dev-request(a)list.inf.unibe.ch wrote: > > thanks doru this is important for the credibility of the community. > > >> On 25 Jun 2019, at 00:29, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Oh. Thanks for the report. We will fix that. >> >> Doru

4 years, 10 months

about http://www.moosetechnology.org failing

by Stéphane Ducasse

Doru can you tell us how we can fix the fact that http://www.moosetechnology.org is failing. Stef -------------------------------------------- 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

4 years, 10 months

Call for sponsors is open - Smalltalks Conference 2019

by Mariano Martinez Peck

Greetings all, I am contacting you on behalf of FAST organization [1] in case you may be interested in sponsoring Smalltalks Conference 2019 [2]. Here [3] is a brochure with some details about the conference, what we do and the importance of the sponsors [4]. We provide different categories to suite different possibilities. If you are interested or have questions please contact me and I can give you all the details about the categories or any further information you may want. We would also appreciate if you can help us pass the word about it [5] (either by mail, linkedin, forums, google groups, mailing lists, twitter, or whatever). Kind regards, PS: Sorry for the multiple copies you may get. [1] https://www.fast.org.ar/ [2] https://smalltalks2019.fast.org.ar/ [3] https://drive.google.com/open?id=1IFjFrWeW-tpJhIkENNJE5pPIytquaDzF [4] https://www.fast.org.ar/get-involved/sponsorship [5] https://twitter.com/fast_arg/status/1128015197636050945 -- Mariano Martinez Peck Email: marianopeck(a)gmail.com Twitter: @MartinezPeck LinkedIn: www.linkedin.com/in/mariano-martinez-peck <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> Blog: https://marianopeck.wordpress.com/

4 years, 10 months

IWST - Kind reminder: submission deadline 15th 2019

by Anne Etien

IWST 19 Information and Call For Papers IWST19 — International Workshop on Smalltalk Technologies Cologne, Germany; August 27-29th, 2019 Goals and scopes The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: • Short position papers describing emerging ideas • Long research papers with deeper description of experiments and of research results. • Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. Important Dates • Submission deadline: June 15th, 2019 • Notification deadline: July 20th, 2019 • Workshop: between August 27th and 29th, 2019 Topics We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: • Aspect-oriented programming, • Design patterns, • Experience reports, • Frameworks, • Implementation, new dialects or languages implemented in Smalltalk, • Interaction with other languages, • Meta-programming and Meta-modeling, • Tools Best Paper Award To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be eligible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. Publication Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.sigplan.org/Resources/Author/ <http://www.sigplan.org/Resources/Author/>. This site also contains links to useful informations on how to write effective submissions. Submission All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst19 <https://easychair.org/conferences/?conf=iwst19> Program chairs • Anne Etien (Université de Lille, France) • Loïc Lagadec (Ensta Bretagne, France)

4 years, 11 months

about URL

by Stéphane Ducasse

BTW, http://www.moosetechnology.org <http://www.moosetechnology.org/> seems to be wrong. http://moosetechnology.org <http://moosetechnology.org/> seems to be correct. Can we do something to get both working? Stef -------------------------------------------- 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

4 years, 11 months

could we create a doc folder for FAMIXNG on the moose git account?

by Stéphane Ducasse

Julien, Benoit, Cyril? May be adding link to the https://github.com/moosetechnology/moose-wiki/ Stef -------------------------------------------- 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

4 years, 11 months

← Newer
1
2
3
4
5
6
7
...
663
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev