- Moose-dev - INF Mailman

by Pavel Krivanek

Dear Pharo users and dynamic language lovers: We have released Pharo <https://pharo.org/> version 12! What is Pharo? Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. - Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. - Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! - Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! - Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. - Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> ... more on the Pharo Features page <http://www.pharo.org/features>. In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo120Chang…> Some highlights of this amazing version: Highlights New breakpoint system The debug point system is a breakpoint model that supersedes the previous implementation of breakpoints and watchpoints. They are configurable, composable, and extensible. The traditional breakpoints remain available, including conditional breakpoints, one-time breakpoints, and object-centric breakpoints. Additionally, there are new types of breakpoints, such as chained-breakpoints, which condition the activation of certain breakpoints on the triggering of others (e.g., breakpoint B only activates if breakpoint A is hit first). Debug points also feature a dedicated browser and integration options. Tools - Scalable fluid class syntax is now the default one - Preparing the introduction of the Bloc graphic system by migrating more tools to Spec2 widgets - Spec2 UI framework enhancements to support GTK 4 - Leaner version of the Metacello package manager - More robust and strict mode for FFI System - New architecture for refactorings and domain specific transformations - Code loading speed improvement - Fast browsing via fully optimized package tags - Optmized memory usage via optimized method protocols - Compiler simplifications and improvements Virtual machine - Massive image support with permanent space - String/ByteArray comparison speed up Development Effort This new version is the result of 1895 Pull Requests integrated just in the Pharo repository. We have closed 865 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: - http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> - http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> - http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> - http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> - http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> - http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> - http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> - http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> Contributors We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 12.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. The Pharo Team Discover Pharo: https://pharo.org/features Try Pharo: http://pharo.org/download <https://pharo.org/download> Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation>

1 year, 2 months

1
0
0 0

Fwd: [Pharo-users] [ ANN ] Pharo Days 2016

by Tudor Girba

> Begin forwarded message: > > From: Sven Van Caekenberghe <sven(a)stfx.eu> > Subject: [Pharo-users] [ ANN ] Pharo Days 2016 > Date: December 9, 2015 at 9:52:09 AM EST > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>, Pharo Development List <pharo-dev(a)lists.pharo.org>, Pharo Business <pharo-business(a)lists.pharo.org> > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Dear fellow Pharoers, > > Mark your calendars: on Thursday March 31 & Friday April 1 we are organising the Pharo Days 2016. This year we moved the location to Namur, Belgium, just a bit south of Brussels, at the very beautiful location of the ‘Cercle de Wallonie’ overlooking the river Meuse. > > We’ll update the following page moving forward. > > https://medium.com/concerning-pharo/pharo-days-2016-c52fe4d7caf > > You can ask questions on any of the Pharo mailing lists or you can email the Pharo Board. > > Let's make this another success, together ! We hope to see as many of you as possible. > > -- www.tudorgirba.com "We are all great at making mistakes."

1 year, 3 months

4
3
0 0

new buses in MooseIDE

by Nicolas Anquetil

concretisation of the discussion of this morning on buses: https://github.com/moosetechnology/MooseIDE/issues/320 it would possibly also solve the problem of tools asking for data of a given type (if the bus forward the request to the tools it is connected to), thus solving nicolas -- Nicolas Anquetil RMod team -- Inria Lille

3 years, 8 months

1
0
0 0

ISWT20 Deadline extension

by Vincent Aranega

Hi everyone, We received multiple demands to postpone the IWST deadline. To increase papers quality and number, we decided to postpone the deadline to the 28th of July (https://esug.github.io/2020-Conference/cfpIWST2020.html). We hope this new deadline will give all the authors more time to polish their papers! Thanks to all for your submissions and contributions, let's keep the great spirit and legacy of IWST a reality! Vincent Aranega

4 years, 11 months

1
0
0 0

IWST 2020 Edition

by Vincent Aranega

Hi everyone, In light of the continued uncertainty surrounding the Covid-19 situation, to guarantee the safety and well-being of all, the IWST Steering Committee has decided to move to a virtual event format for this year to be held Sept. 29th and 30th. The 2020 paper review, WiP submission and acceptance processes will proceed normally with a modification of the upcoming deadlines: - Submission deadline: July 15th, 2020 - Notification deadline: September 8th, 2020 - Workshop: September 29-30th, 2020. Like last year, we are very proud to announce a Best Paper Award. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers. We are also happy to announce that accepted papers will be published in the ACM Digital Library. We will follow up with further details on conference organization, presentation formats, and howto guides. The global idea is to collect all required material a week ahead of schedule to prevent any live technical issue: slides, but also video. Only the post presentation Q&A sessions will be interactive. IWST has now a significant history and has served for years as a smart playground for young researchers to practice writing articles & presenting results. In parallel, senior researchers take benefit from IWST to expose mature work and propose some retrospective or draw future directions. Mixing these two kinds of contributors makes IWST that attractive. Let’s do the 2020 edition conformed to this legacy https://esug.github.io/2020-Conference/cfpIWST2020.html Vincent Aranega Loïc Lagadec

5 years, 1 month

1
0
0 0

19 th INTERNATIONAL CONFERENCE ON SOFTWARE AND SYSTEMS REUSE

by Stéphane Ducasse

This may interest some of you. I’m PC chair of the following conference. S. FIRST CALL FOR PAPERS - ICSR 2020, November 9-11, 2020, Hammamet - TUNISIA 19 th INTERNATIONAL CONFERENCE ON SOFTWARE AND SYSTEMS REUSE www.icsr2020.org The International Conference on Software and Systems Reuse (ICSR) is the premier event in the field of software reuse research and technology. The main goal of ICSR is to present the most recent advances and breakthroughs in the area of software reuse and to promote an intensive and continuous exchange among researchers and practitioners. The 19th International Conference on Software and Systems Reuse (ICSR-2020) will be held on November 9-11 2020, in Hammamet, Tunisia. The guiding theme of this edition is: *Reuse in emerging software engineering practices* We invite submissions on new and innovative research results and industrial experience reports dealing with all aspects of software reuse within the context of the modern software development landscape, characterized by: 1) Large ecosystems of reusable, open-source components and service-oriented, containerized cloud-hosted applications; 2) Context-aware (IoT) applications, which combine a complex and heterogeneous mix of ever more powerful hardware and evolving software frameworks and containers; and 3) The resurgence of AI as both, (i) an enabling technology for reuse for domain engineering (e.g. domain ontologies, identification of reusable assets) and application engineering (e.g. component retrieval), and (ii) an object of reuse that addresses the full lifecycle and scope of “intelligent” software components, i.e. well beyond the simple (re)use of machine learning libraries. These developments have had important—and sometimes contradictory—effects on reuse theory and practice. We welcome papers dealing with : 1) Reuse organizational, managerial, economic, and legal issues, in general, and as they pertain to the new development landscape, 2) Technical aspects of reuse, in general (see full CFP at www.icsr2020.org), and as they pertain to large ecosystems of open-source libraries (npm, pip, etc), IoT frameworks, and machine learning artefacts (business components, models, libraries, training data, etc.), and 3) Software reuse in industry (success & failure stories; success factors and lessons learned; ROI studies). As with previous editions, accepted papers will appear in the conference proceedings, to be published by Springer’s Lecture Notes in Computer Science. New this edition, the program committee will award a Best Paper Award to the best paper in terms of, 1) originality, 2) presentation, and 3) impact. The finalists will be submitted to a special issue of a refereed journal. *Research paper abstracts due June 19th, 2020, full papers due July 3rd, 2020*. *Please check the conference site for more information: www.icsr2020.org* -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / 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 -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / 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

5 years, 4 months

1
0
0 0

Roassal unbounded expandable

by Nicolas Anquetil

hello, I am trying to achieve something like RTInteractionExample>>exampleExpandable but with several levels of expansion: a node with nodes inside with nodes inside and each container node can be "opened" (expanded) or closed. Not sure how to do it and mainly how to resize all the ancestors of a node when an inner node is expanded imagine for example representing the pharo class hierarchy as a single Object node, clicking on the node expand it and shows all its subclasses inside, clicking on a subclass expands it, ... Any suggestion ? nicolas -- Nicolas Anquetil RMod team -- Inria Lille

5 years, 4 months

2
4
0 0

Call for reviewers for Roassal3

by Alexandre Bergel

TL;DR: Reviewing form for Roassal3: https://docs.google.com/forms/d/1-8CJM5_TDu3HBE2d_2dPjqq1pTLZRuauMtPcZZYZXI… Longer version: Dear Community, Right after ESUG 2019 we released a beta version of Roassal3, and we got many very constructive feedbacks from all over the World. We thank you for this. We really tried to improve Roassal3 and specially to provide a smooth and intuitive API to lower the entrance bar for Roassal3. Now is time to enter a new reviewing phase. Our ultimate goal is to provide the visualization engine that the Pharo and Smalltalk communities deserve. The GiHub page contains some information, including a small tutorial: https://github.com/ObjectProfile/Roassal3 Additional tutorials will soon come. You can install Roassal3 either from the catalog (just look for Roassal3), or execute the following instruction: Metacello new baseline: ‘Roassal3’; repository: ‘github://ObjectProfile/Roassal3’; load. Roassal3 comes with many examples. You should look for the package: Roassal3-Examples We would like to end the reviewing page at the end of March 2020. A second edition of Agile Visualization will begin after March 31. Your comment will definitely have an impact on this new book. Reviewers of Roassal3 will: - Have their name listed in Roassal3's website - Have their name listed in the new edition of Agile Visualization - Have a beer next time we meet at ESUG or at Annual Smalltalk meetup in Palo Alto - Make the Pharo community stronger, really. Here is the google form to gather your feedback: https://docs.google.com/forms/d/1-8CJM5_TDu3HBE2d_2dPjqq1pTLZRuauMtPcZZYZXI… Thanks! The Roassal3 development team

5 years, 4 months

1
0
0 0

[ANN] Hashtable on pharo-contributions

by Cyril Ferlicot

Hi! In Moose there is a project call "Hashtable". The goal of this project is to provide faster collections when they have a big number of elements. I think this is something that can be useful for more than just Moose so I extracted it to pharo-contributions so that we can use it and improve it more. https://github.com/pharo-contributions/Hashtable Have a nice day. -- Cyril Ferlicot https://ferlicot.fr

5 years, 5 months

1
0
0 0

Re: Do you need a small objective

by Nour Jihene Agouf

Le mar. 3 déc. 2019 à 12:34, Nour Jihene Agouf <a.n.djihan(a)gmail.com> a écrit : > > > Le mar. 3 déc. 2019 à 12:09, Stéphane Ducasse <stephane.ducasse(a)inria.fr> > a écrit : > >> >> >> On 3 Dec 2019, at 11:46, Nour Jihene Agouf <a.n.djihan(a)gmail.com> wrote: >> >> Hello, >> >> The ClassNames Blueprint is based on packages (package models). There is >> no package model in the moose panel when generating an mse file of a >> certain project. >> >> >> How do you import it. >> > "Import model from MSE file" > >> let us move this discussion to the moose mailing0-list >> >> However, if we import FAMIX smalltalk model from the current image we get >> "all package models" in the moose panel which shows a FAMIXPackageGoup of >> the selected packages which we can later on visualize. >> This way the FeatureSelector (first layer) from my thesis project will be >> replaced by: directly selecting the packages we want to visualize from the >> moose panel and calling the new visualize method. >> >> Basically these will be the steps: >> 1- Import FAMIX smalltalk model from the current image, >> 2- click on all package models, >> 3- "self visualiseCNB" => this method will visualize the ClassNames >> Blueprint of the selected packages. >> >> >> No click we should be able to program that. >> > Do you mean a ClassNames Blueprint option in the navigation panel? > >> Then and only then we can have an action in the menu. >> > >> Stef >> >> >> Nour >> >> >> Le lun. 25 nov. 2019 à 21:57, Nour Jihene Agouf <a.n.djihan(a)gmail.com> a >> écrit : >> >>> Okey I'm on it :) >>> >>> Le lun. 25 nov. 2019 à 21:32, Stéphane Ducasse < >>> stephane.ducasse(a)inria.fr> a écrit : >>> >>>> here is what I suggest. >>>> >>>> You create a separate package that should be the only one manipulating >>>> Moose metamodel. >>>> This way your project will work without Moose and when you load this >>>> extra package, it will work with Moose. >>>> >>>> S. >>>> >>>> On 25 Nov 2019, at 21:13, Nour Jihene Agouf <a.n.djihan(a)gmail.com> >>>> wrote: >>>> >>>> Okey, I will :) >>>> >>>> Le lun. 25 nov. 2019 à 21:09, Stéphane Ducasse < >>>> stephane.ducasse(a)inria.fr> a écrit : >>>> >>>>> >>>>> >>>>> Hello, >>>>> >>>>> Yes that would be great! >>>>> >>>>> >>>>> Ok we will come back with a list >>>>> The first one is to make sure that your visualsiation (class name >>>>> blueprint can run on top of Moose) >>>>> you should ask for help on discord about Moose). >>>>> >>>>> >>>>> And about the visa, unfortunately there is no available dates to >>>>> submit my visa application;, the closest date is in January 2020. Taking >>>>> under consideration the time for the file processing which is about 2 to 3 >>>>> months, should I ask Alexia for an other promise of employment starting >>>>> from 01/03/2020? I hope I receive the hosting agreement before January, >>>>> However, I don't know if this delay has other complications, if so let me >>>>> know please. >>>>> >>>>> >>>>> no ask again >>>>> >>>>> >>>>> Nour >>>>> >>>>> >>>>> Le lun. 25 nov. 2019 à 17:19, Stéphane Ducasse < >>>>> stephane.ducasse(a)inria.fr> a écrit : >>>>> >>>>>> Hi nour >>>>>> >>>>>> We are discussing with Oleksandr and we were thinking if we should >>>>>> propose you some small objectives >>>>>> so that you can learn more waiting for your visa. >>>>>> >>>>>> So let me know. >>>>>> >>>>>> Stef >>>>>> -------------------------------------------- >>>>>> Stéphane Ducasse >>>>>> http://stephane.ducasse.free.fr / 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 >>>>>> >>>>>> >>>>> -------------------------------------------- >>>>> Stéphane Ducasse >>>>> http://stephane.ducasse.free.fr / 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 >>>>> >>>>> >>>> -------------------------------------------- >>>> Stéphane Ducasse >>>> http://stephane.ducasse.free.fr / 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 >>>> >>>> >> -------------------------------------------- >> Stéphane Ducasse >> http://stephane.ducasse.free.fr / 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 >> >>

5 years, 6 months

2
2
0 0

Re: [Pharo-dev] FOSDEM rooms are available

by Santiago Bragagnolo

I could present TaskIT of course, but i don't feel it matching in the proposed categories. There is not debugging, nor emerging minimalist language nor research tools. I will check on the other rooms to see if i find a place where i can do it. El lun., 28 oct. 2019 a las 21:00, ducasse (<stepharo(a)netcourrier.com>) escribió: > > > On 28 Oct 2019, at 18:15, Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com> wrote: > > That is great. We should post in all of them if possible. > I think that Steven could show object centric debugging, someone (anne > maybe? ) present moose. and for minimalistic experimental emerging > languages carolina could propose candle and the bootstrap processes. > I think that Steven and Carolina talks are mature enough after all the > trials, and a moose talk could be really cool. Maybe Julien's SQL or > Benoit's translations should be really good for catching potential students > and specially some investment capital for the team :). > > Sadly me i don't have much to show :(. > But if we have the stand i plan to be there. > > > TaskIt? > I could do a presentation of Pharo in the minimalist…. and carolina a talk > showing how to bootstrap. > > > > > > El lun., 28 oct. 2019 a las 16:41, ducasse (<stepharo(a)netcourrier.com>) > escribió: > >> >> https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ >> I do not know in which one we want to participate >> >> Debugging Tools >> Minimalistic, Experimental and Emerging Languages >> Open Research Tools and Technologies >> >> How do we coordinate? >> >> S. >> > >

5 years, 6 months

3
10
0 0

Re: Do you need a small objective

by Stéphane Ducasse

> On 3 Dec 2019, at 11:46, Nour Jihene Agouf <a.n.djihan(a)gmail.com> wrote: > > Hello, > > The ClassNames Blueprint is based on packages (package models). There is no package model in the moose panel when generating an mse file of a certain project. How do you import it. let us move this discussion to the moose mailing0-list > However, if we import FAMIX smalltalk model from the current image we get "all package models" in the moose panel which shows a FAMIXPackageGoup of the selected packages which we can later on visualize. > This way the FeatureSelector (first layer) from my thesis project will be replaced by: directly selecting the packages we want to visualize from the moose panel and calling the new visualize method. > > Basically these will be the steps: > 1- Import FAMIX smalltalk model from the current image, > 2- click on all package models, > 3- "self visualiseCNB" => this method will visualize the ClassNames Blueprint of the selected packages. No click we should be able to program that. Then and only then we can have an action in the menu. Stef > > Nour > > > Le lun. 25 nov. 2019 à 21:57, Nour Jihene Agouf <a.n.djihan(a)gmail.com <mailto:a.n.djihan@gmail.com>> a écrit : > Okey I'm on it :) > > Le lun. 25 nov. 2019 à 21:32, Stéphane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> a écrit : > here is what I suggest. > > You create a separate package that should be the only one manipulating Moose metamodel. > This way your project will work without Moose and when you load this extra package, it will work with Moose. > > S. > >> On 25 Nov 2019, at 21:13, Nour Jihene Agouf <a.n.djihan(a)gmail.com <mailto:a.n.djihan@gmail.com>> wrote: >> >> Okey, I will :) >> >> Le lun. 25 nov. 2019 à 21:09, Stéphane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> a écrit : >>> >>> >>> Hello, >>> >>> Yes that would be great! >> >> Ok we will come back with a list >> The first one is to make sure that your visualsiation (class name blueprint can run on top of Moose) >> you should ask for help on discord about Moose). >> >>> >>> And about the visa, unfortunately there is no available dates to submit my visa application;, the closest date is in January 2020. Taking under consideration the time for the file processing which is about 2 to 3 months, should I ask Alexia for an other promise of employment starting from 01/03/2020? I hope I receive the hosting agreement before January, However, I don't know if this delay has other complications, if so let me know please. >> >> no ask again >>> >>> Nour >>> >>> >>> Le lun. 25 nov. 2019 à 17:19, Stéphane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> a écrit : >>> Hi nour >>> >>> We are discussing with Oleksandr and we were thinking if we should propose you some small objectives >>> so that you can learn more waiting for your visa. >>> >>> So let me know. >>> >>> Stef >>> -------------------------------------------- >>> Stéphane Ducasse >>> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <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 >>> >> >> -------------------------------------------- >> Stéphane Ducasse >> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <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 >> > > -------------------------------------------- > Stéphane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <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 > -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / 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

5 years, 7 months

1
0
0 0

Internship for a Master research in computer science

by Jannik Laval

Dear colleagues, You will find, in the following link, a proposal for a Master research in computer science or equivalent, for February 2020 at the DISP laboratory, Lyon. https://www.disp-lab.fr/?q=fr/content/stage-m2-banc-de-tests-d%E2%80%99%C3%…<https://www.disp-lab.fr/?q=fr/content/stage-m2-banc-de-tests-d’échanges-de-…> Best regards -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet en Systèmes d'Information IUT Lumière, Université Lumière Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

5 years, 7 months

1
0
0 0

Play Page File Extension

by Sean P. DeNigris

Is there a benefit to giving saved play pages a custom extension (.ph)? I tried to DND one into a P7 image and it failed because there is no handler for that extension, even thought it's "just code"... ----- Cheers, Sean -- Sent from: http://forum.world.st/Moose-f1310756.html

5 years, 8 months

2
2
0 0

Re: [Pharo-dev] FOSDEM rooms are available

by Esteban Lorenzano

> On 29 Oct 2019, at 11:05, tesonep(a)gmail.com wrote: > > Yes, I will love to participate. > I think that the most important is to have a good presence as a stand > in the hall. > I will love to do that. I will be there too, at least one day. Esteban > About the talks, we can propose anything, even something about the VM. > We have to analyze what are the things that are applicable to other > languages and technologies, to avoid comments like: "that happen to > you because you have an image". > Also we need to show us open and good to team work with other technologies. > > Thanks! > > On Tue, Oct 29, 2019 at 10:25 AM Santiago Bragagnolo > <santiagobragagnolo(a)gmail.com <mailto:santiagobragagnolo@gmail.com>> wrote: >> >> >> To whom does not know, FOSDEM is one of the biggest Open source conferences. It is free, it does not require subscription, and it happens during a weekend (1 and 2 february) at bruxelles at the university ULB ( https://fosdem.org/2020/practical/transportation/) . It requires some human engagement only. >> This is a good place not only for Pharo, but for all open source projects Smalltalk related. And finally for smalltalk it self. >> >> On the available rooms where we could show something >> >> IOT (https://fosdem.org/2020/schedule/track/internet_of_things/ ) >> Allex? maybe you can show some of the things we are doing here? >> Mariano Peck? I don't know if your IOT work is or not open source. But if it is. it could be a good place for showing >> >> BigData (https://fosdem.org/2020/schedule/track/hpc_big_data_and_data_science/) >> I could propose the EQL experiment with Map reduce? Is it a good Idea? . >> Matteo You could present something on debugging nodes. >> Oleks I remember you had some big data related stuff (sorry for the lack of detail awareness :) ) >> >> Communication (https://fosdem.org/2020/schedule/track/collaborative_information_and_conten… >> https://fosdem.org/2020/schedule/track/coding_for_language_communities/ ) >> Offray! I think there is space for graphoscope in here. If you can give a talk, great, if not, i propose my self to be the speaker (of course in that case i will need some couching and teaching on the usage). >> >> Debugging Tools >> Matteo! you could also propose your work in here >> Steven You have already a talk prepared no? >> Thomas You have already a talk prepared no? >> Guille I know you are completely out of reach, but, what about your debugging multi level for the VM? If you want we can propose it together with Pablo. >> >> >> Minimalistic / Emerging Language >> Steph with Pharo >> Carolina The bootstraping for minimallistic language is a good talk and it would not require much preparation since you have already a talk prepared >> Steph/Pablo maybe something on stateful traits? >> >> Open research tools >> Anne/Nico/Cyril/Julian/Benoit Moose? We have to have a talk on moose. Or even many. We could propose moose as platform, but i think it would be better to present it by it fruits. The same as before, i would not mind to give the presentation if couching and slides are provided. >> Serge PolyMath?? >> Nick Lands! Such a beatiful project. Not sure if it completely fit in here. I think so. Sorry if not :). >> >> >> On the pharo stand >> >> I am doing what is required to have a stand for Pharo this year. >> I will keep you updated, if we got it, i would really like to have posters not only of Pharo, but also of our more stable and powerful frameworks, the research teams and enterprises that work with it . And of course I will need some help for the stand (specially if it happens that i have some talk) >> >> Maybe we could use this thread for discussing organization and a second one to gather abstracts and applications. >> >> Santiago >> >> >> >> >> >> >> >> El mar., 29 oct. 2019 a las 9:29, Santiago Bragagnolo (<santiagobragagnolo(a)gmail.com>) escribió: >>> >>> I could present TaskIT of course, but i don't feel it matching in the proposed categories. There is not debugging, nor emerging minimalist language nor research tools. I will check on the other rooms to see if i find a place where i can do it. >>> >>> >>> >>> El lun., 28 oct. 2019 a las 21:00, ducasse (<stepharo(a)netcourrier.com>) escribió: >>>> >>>> >>>> >>>> On 28 Oct 2019, at 18:15, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: >>>> >>>> That is great. We should post in all of them if possible. >>>> I think that Steven could show object centric debugging, someone (anne maybe? ) present moose. and for minimalistic experimental emerging languages carolina could propose candle and the bootstrap processes. >>>> I think that Steven and Carolina talks are mature enough after all the trials, and a moose talk could be really cool. Maybe Julien's SQL or Benoit's translations should be really good for catching potential students and specially some investment capital for the team :). >>>> >>>> Sadly me i don't have much to show :(. >>>> But if we have the stand i plan to be there. >>>> >>>> >>>> TaskIt? >>>> I could do a presentation of Pharo in the minimalist…. and carolina a talk showing how to bootstrap. >>>> >>>> >>>> >>>> >>>> >>>> El lun., 28 oct. 2019 a las 16:41, ducasse (<stepharo(a)netcourrier.com>) escribió: >>>>> >>>>> >>>>> https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ >>>>> I do not know in which one we want to participate >>>>> >>>>> Debugging Tools >>>>> Minimalistic, Experimental and Emerging Languages >>>>> Open Research Tools and Technologies >>>>> >>>>> How do we coordinate? >>>>> >>>>> S. >>>> >>>> > > > -- > Pablo Tesone. > tesonep(a)gmail.com <mailto:tesonep@gmail.com>

5 years, 8 months

1
0
0 0

Re: [Pharo-dev] FOSDEM rooms are available

by Santiago Bragagnolo

That is great. We should post in all of them if possible. I think that Steven could show object centric debugging, someone (anne maybe? ) present moose. and for minimalistic experimental emerging languages carolina could propose candle and the bootstrap processes. I think that Steven and Carolina talks are mature enough after all the trials, and a moose talk could be really cool. Maybe Julien's SQL or Benoit's translations should be really good for catching potential students and specially some investment capital for the team :). Sadly me i don't have much to show :(. But if we have the stand i plan to be there. El lun., 28 oct. 2019 a las 16:41, ducasse (<stepharo(a)netcourrier.com>) escribió: > > https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ > I do not know in which one we want to participate > > Debugging Tools > Minimalistic, Experimental and Emerging Languages > Open Research Tools and Technologies > > How do we coordinate? > > S. >

5 years, 8 months

1
0
0 0

The Lands Platform at SLE 2019: Pharo magic inside

by Nick Papoylias

The Lands Platform: Lan.guages and D.omain S.yntax, @sleconf 2019, co-located with @splashcon https://youtu.be/HMgJK8mVPYw Showcasing live magic tricks powered by the @pharoproject Best, Nick

5 years, 8 months

3
3
0 0

Glamour: Updating Dependent Presentations

by Sean P. DeNigris

Here's a snippet from my builder method: ... views do: [ :d | container tree act: [ :tree :projects | "change the model." tree update ] iconName: #back on: $n entitled: 'New Project'; ... ]. Each tree represents a different view on the same data. When the action is performed, they all need to be updated. I tried replacing `tree update` with `container update`, but that didn't work. Ideas? ----- Cheers, Sean -- Sent from: http://forum.world.st/Moose-f1310756.html

5 years, 9 months

2
2
0 0

Moose 8 - Progress on generator management

by Cyril Ferlicot

Hi! Today I finished a refactoring on Moose 8 and I wanted to keep everyone informed. Since Moose 7 we have multiple metamodels and we generate them via a generator. Each metamodel has a FMMetaRepository used to build tools and to query our models. This FMMetaRepository was created by the generators. This had some drawbacks such as: - You need to have your generator in the image to be able to query your model - You cannot write a new metamodel without generator Now this changed, the FMMetaRepository is created and stored in the subclasses of MooseModel specific to the metamodel currently used. The change should be transparent, except that you will need to regenerate your metamodel for it to be effective. Have a nice day. -- Cyril Ferlicot https://ferlicot.fr

5 years, 9 months

1
0
0 0

Saving Moose model in MongoDB

by Jannik Laval

Hi everyone, I am trying to save a moose model into MongoDB, using Voyage (Pharo 7, Moose 8). My problem is that it is not a tree. So I declared MooseEntity as voyageRoot. Now, it seems I have a loop into my graph. Do you have any idea of ho to debug that ? Cheers, -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet IUT Lumière, Université Lumière Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

5 years, 9 months

7
16
0 0

PhD position

by Jannik Laval

[Apologies for Cross-Posting] Dear all, At DISP Lab, at Lyon, France, we have a PhD opening on « Ensuring Interoperability for "smart" information systems". More information are following. What is important is that all the development will be done using Pharo/Moose. If you are interested, please contact me by answering this mail. ===== Ph.D. thesis (CIFRE) Berger Levrault and DISP Lab, Lyon, France Title: Ensuring Interoperability for "smart" information systems Enterprise: Berger Levrault Research Laboratory: DISP Lab Where: Lyon, France Recruitment date: As soon as possible Application deadline: As soon as possible Function: 3 years PhD candidate position in Berger Levrault (CDI). The position will be part time between Berger Levrault and DISP Lab. Research topic : data interoperability, application exchange protocols, service-oriented architecture, event architecture, semantics, monitoring. Context: The need for sharing, exchanging and promoting information from information systems is constantly increasing and now represents a major concern in the various reforms of the local public sector (consolidation of local authorities, implementation of in place in 2016 Hospital Group Territory, Digital Republic). It is therefore essential to design "platforms" capable of providing answers to the rationalisation and simplification of data exchanges between software applications and with the outside world to promote and simplify the application of all these reforms. In addition, service-oriented architectures and event architectures (SOA, EDA) are mature and widely used. At Berger-Levrault, their implementation ensures the scalability and maintainability of solutions. These architectures are characterised by the flexibility and the loose coupling of the subsystems that compose them (ie services, applications, IS ...) and rely on several means (Hohpe & Woolf, 2004) to route the data within this network of systems communicating. At this stage of maturity, we observe that these data exchanges are operational and meet the requirements of interoperability between heterogeneous systems (Leal, 2019). Nevertheless, the number of standards recognised and used by the French public sector, the privileged sector of Berger-Levrault, increases the level of interconnection difficulties (Kurniawan & Ashari, 2015) of the different solutions developed by Berger-Levrault. This is all the more remarkable when it comes to communicating with external solutions or platforms (partners and / or competitors). This multiplicity of exchanges and types of exchanges generates a great deal of complexity and highlights the need to master the exchange system as effectively as possible. Berger Levraut today lacks visibility on existing exchanges and mechanisms to evaluate them (Leal, Guédria, & Panetto, 2019) which complicates the detection of dysfunctions and the discovery of their origins. Moreover, it is essential for the Berger-Levrault applications to be able to adapt to the new rules and standards while continuing to integrate the dematerialization of the public service. The evolution of these modalities has an almost systematic impact on the exchange of data put in place to ensure interoperability. Hence the need to build flexible and scalable exchange architectures and to follow the evolution of these exchanges. These transformations imply a large volume of data exchanged and subject to variations that can be strong during periods of "high attendance" such as elections by electronic vote. The very nature of exchanges can be affected especially with the multiplicity of connected objects (Buyya & Dastjerdi, 2016). These are increasingly used by public institutions for the benefit of the management of city facilities or user services. The increase in volumes of data exchanged therefore implies the implementation of exchange architectures that are able to support the load but also the great variability of the types and frequencies of data production. This requires distributed architectures (in infrastructure and flow), adaptable or even self-adaptable (Gascon-Samson et al 2015) to promote the system's resistance to faults while avoiding potential congestion phenomena. Based on this reflection, a research project was conducted in partnership by Berger-Levrault and the DISP laboratory (Amokrane et al., 2018). These early works have identified a set of scientific and technical barriers: • Lack of visibility on existing interoperability exchanges. Indeed, the current exchanges are not traced and the existing monitoring mechanisms focus mainly on low level information, such as the performance of the infrastructure or the use of the memory, without correlation with business information. In addition, few methods for evaluating interoperability are concerned with the effective evaluation (a posteriori of the implementation) of the interoperability of the data, and few of them are tooled (Leal, Guédria, & Panetto, 2019). • The complexity of trade maintenance. This is due to the lack of traceability of the exchanges, on the one hand, and that of the evolution of the exchange architecture configurations on the other hand. This complicates the identification of failures or dysfunctions and the analysis of their causes, and poses difficulties for the setting up of mechanisms of alerts or significant notifications. In addition, the lack of capitalisation of information relating to trade does not allow to consider a forecast maintenance. • The development of the different modules of the exchange system is manual and the remediation of malfunctions is done in an ad hoc manner. In addition to the cost of development and correction that this implies, this does not meet the responsiveness requirements of some business areas. Hence the need to build adaptable exchange systems using dynamic interoperability hubs (Agostinho, et al., 2016). The objective of this thesis proposal is to produce an approach to the implementation cycle of application exchanges, from design to maintenance, which will enhance the reliability and resilience of the interoperability exchange system. The solution will ultimately orchestrate all the application and service exchanges to ensure optimisation of the use of software and infrastructure resources of public institutions. To meet the needs in terms of interoperability, the work to be carried out is articulated in two axes that we structure as follows: - A flexible architecture for the implementation of interoperability. Here we consider the basic functionalities reflecting the activities necessary for the establishment of the means of interoperability. - A reflexive architecture for managing interoperability at a meta-level. This axis relates to setting up means of administration, monitoring and maintenance of the exchange network set up for interoperability. The work must also incorporate the concepts of security, scalability and usability. Requirements to be met when developing any solution to lift the locks and meet the objectives of this thesis work. ----- Agostinho, C., Ducq, Y., Zacharewicz, G., Sarraipa, J., Lampathaki, F., Poler, R., & Jardim-Goncalves, R. (2016). Towards a sustainable interoperability in networked enterprise information systems: Trends of knowledge and model-driven technology. Computers in Industry, 79, 64 - 76. doi:10.1016/j.compind.2015.07.001 Al-Dhuraibi, Y., Paraiso, F., Djarallah, N., & Merle, P. (2017). Elasticity in cloud computing: state of the art and research challenges. IEEE Transactions on Services Computing, (pp. 430-447). Amokrane, N., Laval, J., Lanco, P., Derras, M., & Moalla, N. (2018). Analysis of Data Exchanges, Contribution to Data Interoperability Assessment. 9th international Conference on Intelligent Systems 2018. Madeira, Portugal. Andary, J. F., & Sage, A. P. (2010). The role of service oriented architectures in systems engineering. Information Knowledge Systems Management, 9(1), 47-74. Belfadel, A., Laval, J., Cherifi, C., & Moalla, N. (2018). Towards service orchestration through software capability profile. I-ESA Interoperability for Enterprise Systems and Applications 2018. Berlin, Germany. Bernus, P., Goranson, T., Gøtze, J., Jensen-Waud, A., Kandjani, H., Molina, A., . . . Turner, P. (2016). Enterprise engineering and management at the crossroads. Computers in Industry, 79, 87 - 102. doi:10.1016/j.compind.2015.07.010 Buyya, R., & Dastjerdi, A. V. (2016). Internet of Things: Principles and paradigms. Elsevier. Cabot, J., Clarisó, R., Brambilla, M., & Gérard, S. (2017). Cognifying model-driven software engineering. Federation of International Conferences on Software Technologies: Applications and Foundations (pp. pp. 154-160). Springer. Chappell, D. (2004). Enterprise Service Bus. : O'Reilly Media, Inc. Cheung, A. K., & Jacobsen, H. A. (2010). Load balancing content-based publish/subscribe systems. ACM Transactions on Computer Systems (TOCS). Chhun, S., Moalla, N., & Ouzrout, Y. (2016). QoS ontology for service selection and reuse. Journal of Intelligent Manufacturing, 27(1), 187-199. Crosby, M., Pattanayak, P., Verma, S., & Kalyanaraman, V. (2016). Blockchain technology: Beyond bitcoin. Applied Innovation, 2(6-10). Curry, E. (2004). Message-oriented middleware, Middleware for communications,. Czarnecki, K., Eisenecker, U., Glück, R., Vandevoorde, D., & Veldhuizen, T. (2000). Generative programming and active libraries. Generic Programming (pp. pp. 25-39). Berlin, Heidelberg.: Springer. Erl, T. (2005). Service-oriented architecture: concepts, technology, and design. Prentice Hall Professional Technical Reference. Fahad, M., Moalla, N., & Bouras, A. (2012). Detection and resolution of semantic inconsistency and redundancy in an automatic ontology merging system. Journal of Intelligent Information Systems, 39(2), 535-557. Fahad, M., Moalla, N., Bouras, A., Abdul Qadir, M., & Farukh, M. (2011). Towards Classification of Web Ontologies for the Emerging Semantic Web. Journal of Universal Computer Science, 17(7), 1021-1042. Fülöp, L. J., Tóth, G., Rácz, R., Pánczél, J., Gergely, T., Beszédes, A., & Farkas, L. (2010). Survey on complex event processing and predictive analytics. the Fifth Balkan Conference in Informatics, (pp. pp. 26-31). Gascon-Samson, J., Garcia, F. P., Kemme, B., & Kienzle, J. (2015). Dynamoth: A scalable pub/sub middleware for latency-constrained applications in the cloud. In 2015 IEEE 35th International Conference on Distributed Computing Systems , (pp. pp. 486-496). Gokhale, A., Schmidt, D. C., Natarajan, B., & Wang, N. (2002). Applying model-integrated computing to component middleware and enterprise applications. Communications of the ACM, (pp. 65-70). Hachicha, M., Moalla, N., Fahad, M., & Ouzrout, Y. (2015). Performance assessment architecture for collaborative business processes in BPM-SOA based environments. International journal of Data & Knowledge Engineering, 105, 73-89. Hohpe, G., & Woolf, B. (2004). Enterprise integration patterns: Designing,building, and deploying messaging solutions. Addison-Wesley Professional. Khare, S., Sun, H., Zhang, K., Gascon-Samson, J., Gokhale, A., Koutsoukos, X., & Abdelaziz, H. (2018). Scalable edge computing for low latency data dissemination in topic-based publish/subscribe. In 2018 IEEE/ACM Symposium on Edge Computing (SEC) (pp. pp. 214-227). IEEE. Kurniawan, K., & Ashari, A. (2015). Service orchestration using enterprise service bus for real-time government executive dashboard system. 2015 International Conference on Data and Software Engineering (ICoDSE), (pp. 207-212). Yogyakarta. doi:10.1109/ICODSE.2015.7436999 Laval, J., Cherifi, C., & Cheutet, V. (2018). Towards the measurement of Enterprise Information Systems agility to support EIS improving projects. International Journal of Agile Systems and Management, 11(3):222–246. Leal, G. D. (2019). Support à la décision pour l'analyse de l'interopérabilité des systèmes dans un contexte d'entreprises en réseau. (Doctoral dissertation, Université de Lorraine). Leal, G., Guédria, W., & Panetto, H. (2019). Interoperability Assessment: A Systematic Literature Review. Computers in Industry (In Press). Luckham, D. C. (2011). Event processing for business: organizing the real-time enterprise. John Wiley & Sons. Mallek, S. (2012). Contribution au développement de l’interopérabilité en entreprise : vers une approche anticipative de détection de problèmes d’interopérabilité dans des processus collaboratifs. Object Management Group. (2006). Méta Object Facility (MOF) 2.0 Core Specification. Panettoa, H., Zdravkovicc, M., Jardim-Goncalvesd, R., Romeroe, D., Cecilg, J., & Mezgárh, I. (2016). New perspective for the future interoperable enterprise systems. Computers in Industry, s.l. : Elsevier, 79, 47-63. doi:10.1016/j.compind.2015.08.001 WSO2. (2015). The Evolution of Integration: A Comprehensive Platform for a Connected Business. White Paper. Récupéré sur http://wso2.com/ -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet IUT Lumière, Université Lumière Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

5 years, 9 months

1
0
0 0

Moose wiki

by badetitou＠gmail.com

Hello moose developer! First of all, thanks for the little meeting at Esug19! One of the point during the meeting was: do we have documentation about the new features introduced in moose? The answer is: YES! It's still work in progress (as the work on Moose 8). I'm trying to create a moose-wiki (as https://github.com/pharo-open-documentation/pharo-wiki). You can find it here: https://moosetechnology.github.io/moose-wiki/ (w eb version) and here: https://github.com/moosetechnology/moose-wiki (github version). Most of the documentation come from themoosebook and https://github.com/SquareBracketAssociates/Booklet-FamixNG and part of the documentation are new. I'm also trying to collect all the famix parsers (to create mse files) we have and the meta-models. I think we can also create links to great moose-projects (not directly in a moose image but you can load it in moose (like FAST)). I also create linked to blog posts that describes the protocol to analyze projects with moose (as https://fuhrmanator.github.io/2019/07/29/AnalyzingJavaWithMoose.html) If you have one, please send me an email ;-) Benoît Verhaeghe @badetitou PHD student at: RMoD - Inria Lille - Nord Europe R&D developer at Berger-Levrault - France

5 years, 9 months

3
2
0 0

Moose meeting @ESUG19?

by Anne Etien

Hi, I would like to organise a meeting around Moose at ESUG19, to explain you what we have done this year, where we are going and discuss with you what you are expecting and how you can contribute. If we are enough, we can do that either today (Wednesday) just after lunch at 13h or tomorrow Thursday after show us your project. Can you please say if you want to attend and which date you are available? Thanks in advance. Anne

5 years, 10 months

5
4
0 0

PetitJSON

by Jannik Laval

Hi moosers, When loading Moose 7, PetitJson is not included. Is it voluntary ? Cheers, -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet IUT Lumière, Université Lumière Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

5 years, 10 months

3
4
0 0

Using Moose 8.0 with C/C++ (and other languages)

by Galen Tackett

I’ve yet to try anything significant with Moose, either this new version or the prior. Though I did run some C through Verveine C/C++ over a year ago, I don’t remember doing anything with Moose itself. Does Moose 8.0 change the way that you use it for programs in C (and other languages that needed something that the earlier Moose didn’t do by itself)? Sent from my iPad > On Aug 5, 2019, at 5:25 AM, Benoît Verhaeghe <badetitou(a)gmail.com> wrote: > > Hi, > > It is added on instance side of MooseAbstractGroup, as #allWithSubTypesOf: and, #allWithType: > > Cheers, > Benoit > > >> Le lun. 5 août 2019 à 11:06, Tudor Girba <tudor(a)tudorgirba.com> a écrit : >> Hi, >> >> Interesting. Is this added on the instance side or MooseModel? >> >> Cheers, >> Tudor >> >> >> > On Aug 5, 2019, at 11:00 AM, Benoît Verhaeghe <badetitou(a)gmail.com> wrote: >> > >> > Hi all, >> > >> > We have added the method "allUsing:". >> > It takes a Trait as a parameter and will return all the entities in your model that use the trait. >> > >> > Example: >> > mooseModel allUsing: FamixTClass >> > will return all the FamixJavaClass and FamixJavaInnerClass (if FamixJavaInnerClass --|> FamixJavaClass) >> > >> > It will be the main method if you want to query your model with abstract entities. >> > >> > Benoît >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)list.inf.unibe.ch >> > https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -- >> feenk.com >> >> "We can create beautiful models in a vacuum. >> But, to get them effective we have to deal with the inconvenience of reality." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

5 years, 11 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev