Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

Start a nNew thread

Trachel Documentation wanted.

by Bouremel Abd El Hakim

Hello Anybody can help me i need documentation about Trachel . Thanks

6 years, 10 months

Fwd: [Pharo-dev] [JOB][Research] 3 Year Starting Research Positions

by Tudor Girba

> Begin forwarded message: > > From: Marcus Denker <marcus.denker(a)inria.fr> > Subject: [Pharo-dev] [JOB][Research] 3 Year Starting Research Positions > Date: February 20, 2018 at 9:39:42 AM GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > Inria opended a call for starting researchers. This is a three year contract. > > REQUIREMENTS > > - Have a French doctorate or an equivalent international degree > - From 2 to 8 years of experience in research (after the thesis) > - No age or nationality conditions. > - Deadline: April 3rd, 2018 > > Before writing their research program, the applicants are strongly encouraged to contact the teams > or project(s)-teams leaders concerned by their applications. More information on the official website: > https://www.inria.fr/en/institute/recruitment/offers/starting-research-posi… > > MISSION > > Join one of our two lines of research: Tools for Software Maintenance or New Programming > Language Constructs for Software Evolution. > > THE REGION > > Lille is strategically located in Northern Europe with train connections to Paris (1h), London (1h30) > and Brussels (30 min.) The Nord Pas de Calais region is a dynamic area in both industry and research > for computer science with companies that are european leaders in their branch. Lille, the capital of > northern France is an attractive metropolis of over 1 million inhabitants. Cost of living in Lille is lower > than that of very big cities such as Paris and London. > > THE TEAM > > RMoD is an Inria research project team. It consists of 5 permant researchers (Inria CR and DR, as > well as University Assistant Professors) and Engineers, postdocs and students (Master and PhD). > RMoD is an international team with more than 20 members from six countries. > > LINKS: > > RMoD: http://rmod.lille.inria.fr > INRIA Lille: http://www.inria.fr/lille/ > INRIA in General: http://www.inria.fr > Lille: > http://en.wikipedia.org/wiki/Lille > http://wikitravel.org/en/Lille > > Please contact the head of the research team: Stephane.Ducasse(a)inria.fr or one > of the following group members: Nicolas.Anquetil(a)inria.fr, Marcus.Denker(a)inria.fr > > Permanent Link: https://rmod.inria.fr/web/blog/2018-02-19 -- www.tudorgirba.com <http://www.tudorgirba.com/> www.feenk.com <http://www.feenk.com/> "From an abstract enough point of view, any two things are similar."

6 years, 10 months

Fwd: [Esug-list] ESUG 2018 Call for Presentations

by Tudor Girba

> Begin forwarded message: > > From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Subject: [Esug-list] ESUG 2018 Call for Presentations > Date: February 18, 2018 at 8:55:15 AM GMT+1 > To: ESUG Mailing list <esug-list(a)lists.esug.org> > > > Please distribute around :) > > Call-for-Presentations 26rd International Smalltalk Joint Conference > > The ESUG board is pleased to announce that the 26th ESUG conference/summer-school will be held in Cagliari, Italy 10-14 September 2018; with Camp Smalltalk 8-9 September 2018. The conference is co-organized by University of Cagliari and the Agile Group of the faculty of computer science. > > http://www.esug.org/wiki/pier/Conferences/2018/ <http://www.esug.org/wiki/pier/Conferences/2018/> > > This call includes: > > - Developer Forum > - Smalltalk Technology Award > - International Workshop http://www.esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_… <http://www.esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_…> > - Student Volunteer http://www.esug.org/wiki/pier/Conferences/2018/Student-volunteers <http://www.esug.org/wiki/pier/Conferences/2018/Student-volunteers> > > You can support the ESUG conference in many different ways: > =============================================== > - Sponsor the conference. New sponsoring packages are described at > http://www.esug.org/wiki/pier/About/BecomeSponsor <http://www.esug.org/wiki/pier/About/BecomeSponsor> > - Submit a talk, a software or a paper to one of the events. See below. > - Attend the conference. We'd like to beat the previous record of attendance. > > Students can get free registration and hosting if they enrol into the the Student Volunteers program. See below. > Developers Forum: International Smalltalk Developers Conference > > > > Call For Participation > ================ > We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45-60 min for hand-ons tutorial. > > The list of topics for the normal talks and tutorials includes, but is not limited to the following: > > -Micro Services, Container, Cloud, Big Data, > -XP practices, Development tools, Experience reports > -Model driven development, Web development, Team management > -Meta-Modeling, Security, New libraries and frameworks > -Educational material, Embedded systems and robotics > -SOA and Web services, Interaction with other programming languages > -Teaching Pearls and Show us Your Business > -Show your business 10 min session (Get prepared!!) > > > How to submit? > ============ > Submissions deadline is 15 of June 2018 > Notification of acceptance will be on done on the fly. > > Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to Stephane.Ducasse[at]inria.fr <http://inria.fr/> > AND USE THE following header [ESUG 2018 Developers] Title: > Please follow the template below the email will be automatically processed! > Name: > Email: > Abstract: > Bio: > > Any presentation not respecting this form will be discarded automatically. > > International Workshop on Smalltalk Technologies > ====================================== > Read the page: *http://www.esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_18* <http://www.esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_…> > > Technology Award Competition > ======================== > The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/wiki/pier/Conferences/2018/Innovation-Technology-Awards <http://www.esug.org/wiki/pier/Conferences/2018/Innovation-Technology-Awards> > > Student Volunteer Program > ===================== > If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at > > http://www.esug.org/wiki/pier/Conferences/2018/Student-volunteers <http://www.esug.org/wiki/pier/Conferences/2018/Student-volunteers> > We hope to see you there and have fun together. > > > > -------------------------------------------- > Stéphane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > http://www.synectique.eu <http://www.synectique.eu/> / 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 > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org <mailto:Esug-list@lists.esug.org> > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > -------------------------------------------- > Stéphane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > http://www.synectique.eu <http://www.synectique.eu/> / 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 > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -- www.tudorgirba.com <http://www.tudorgirba.com/> www.feenk.com <http://www.feenk.com/> "Problem solving efficiency grows with the abstractness level of problem understanding."

6 years, 10 months

Error in MoosePanel

by Jannik Laval

Dear Moosers, I am trying to use Moose 6.1 (by the way, it is beautiful !) I declared this method that should make visible all RMQLogEntity in the MoosePanel : MooseModel>>allRMQLogEntityGroups <navigation: 'All RMQ Log groups'> ^self allWithType: RMQLogEntity The item "all rmqlogentity" is available in the MoosePanel, but when I click on it, it generate an error (available attached). I probably forget to declare something, but I do not remember which one. Could you help me ? Cheers, Jannik -- ~~Jannik Laval~~ Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

6 years, 10 months

[ANN] MooseQuery documentation

by Cyril Ferlicot

Hello everyone! Some year ago, Moose included a query mechanism called MooseChef. This mechanism worked but was hard to maintain and it was easy to make mistakes in the queries. In 2015 Jean-Christophe Back and Anne Etien created MooseQuery. MooseQuery is a domain-specific language to build navigations and scopes queries for entities in Moose. I helped to improve the performances of MooseQuery in order to use it at Synectique and today I present you a documentation of MooseQuery: https://moosequery.ferlicot.fr/ This documentation cover three axes: - The user documentation: explain how to use MooseQuery to query a model - The developer documentation: explain how to expand a meta-model to make it queriable by MooseQuery and explain how the queries work internally - The API documentation The documentation was already reviewed and enhanced by Anne. If you wish to contribute, you can do a pull request to https://github.com/jecisc/MooseQueryDocumentation. I hope this can help Moose's community. Have a nice day :) -- Cyril Ferlicot https://ferlicot.fr

6 years, 11 months

Notification of modifications in MooseQuery

by Cyril Ferlicot

Hello everyone! Some month ago I sent a mail asking to ensure that all FAMIXEntities could answer to all MooseQuery queries. The answer was no because the community does not want some entities to be able to answer to every query. (For example to have associations that can answer to navigation queries). This bothered me because we already have entities that can answer to #children, #parents, #toScope:, #atScope:... even if it does not make any sense. Now I come back with a proposition to clean this half/half state and to get a clean model query side. I discussed these changes with Anne and she agrees with them. In the current state of MooseQuery we have: - TMetaLevelDependency used by FAMIXEntity that allow querying the children, parents, and scopes of an entity - TEntityMetaLevelDependency using TMetaLevelDependency. It adds the navigation queries. - TAssociationLevelDependency using TMetaLevelDependency. It adds some useful methods to associations for the navigation queries. We have two changes to propose. First. It does not make any sense for TAssociationMetaLevelDependency to use TMetaLevelDependency since an association should not be able to answer to #children, #parents, #toScope:... We propose to remove this usage. I did this change in an image and launched MooseQuery/Chef tests, everything is green. Second. TMetaLevelDependency does not make any sense when we have TEntityMetaLevelDependency. All the methods of TMetaLevelDependency are related to entities. We propose to copy all the methods of TMetaLevelDependency to TEntityMetaLevelDependency and remove it. TMetaLevelDependency has two users: FAMIXEntity and TEntityMetaLevelDependency. Since we copy the methods to the second user, there is no problem with it. The biggest change is that now FAMIXEntity will not implement any Meta trait. It does not need to use any since all its subclasses should not understand generic queries. The only change that needs to be done is to move the caches created on FAMIXEntity to the users of TEntityMetaLevelDependencies. I tried to apply this changes in a quick and dirty way to an image and once again all tests seem to pass. In conclusion, what do we win with this changes? All Famix entities will only understand the queries they can answer to. FAMIXAssociation, FAMIXSourceAnchor, FAMIXSourceLanguage will not understand anymore #children, #parents, #toScope:, #atScope:... Have a nice day :) -- Cyril Ferlicot https://ferlicot.fr

6 years, 11 months

Scala

by Guido Chari

Hi guys, Is there any importer available to generate Moose models for Scala code? Best regards, Guido.

6 years, 11 months

feenk log

by Tudor Girba

Hi, Here is an update of the work on Bloc and GT. As always, please do let us know what you think. Bloc: - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: https://twitter.com/feenkcom/status/955086133519618048 https://twitter.com/feenkcom/status/946482609680539649 - Embedding Bloc elements in Morphic is even easier now: https://twitter.com/feenkcom/status/946676667002556416 - We continued the work towards an interactive creation of a graphical scene: https://twitter.com/feenkcom/status/948492946541858816 - Theme experiment GT: - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: https://twitter.com/feenkcom/status/939394586115563520 - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. Have fun, The feenk team -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

6 years, 11 months

Fwd: [Pharo-dev] Google Summer of Code 2018 with Pharo Consortium

by Serge Stinckwich

---------- Forwarded message ---------- From: Jigyasa Grover <grover.jigyasa1(a)gmail.com> Date: Wed, Jan 10, 2018 at 6:10 AM Subject: [Pharo-dev] Google Summer of Code 2018 with Pharo Consortium To: pharo-dev(a)lists.pharo.org Hello Pharo-ers ! On behalf of the community, I would like to thank each one of you for their significant contribution in the previously concluded *Google Summer of Code 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after this successful stint by applying to participate in the upcoming *Google Summer of Code 2018*. As many of you might know, Google Summer of Code is a global program focused on bringing more student developers into open source software development. Students work with an open source organization on a 3 month programming project during their break from school. Read more about the program here: https://summerofcode.withgoogle.com/ The deadline for organisations to apply is January 23, 2018 which is fast approaching. As an open source evangelist and a Pharo developer, I would like to invite all the experienced members to be a part of the "GSoC 2018 with Pharo Consortium" Team and mentor students. Propose fresh ideas for projects which shall help improve Pharo or volunteer to mentor any of the existing one (Listed here: http://gsoc.pharo.org/). To add your own project idea to the list, visit http://gsoc.pharo.org/#adding-a-proposal Looking forward to an appreciable representation from the Pharo community. Best regards Jigyasa Grover Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email] -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

6 years, 11 months

[ann] gt connector

by Tudor Girba

Hi, Towards the end of last year we worked on GT Connector, a new kind of interface that allows us to exercise and test the limits (or the lack thereof) of Bloc. It looks like this: You can see it in action here: https://twitter.com/feenkcom/status/936109463462965248 In the current implementation, the Connector allows us to navigate and connect example methods. The focus is not on examples, but on the connections. We used examples because the engine was already around and offered us a nice use case. We want to extend it in the near future to other kinds of objects. There are a couple of things that are worth noting: • The editor works live, and the connection points appear and disappear as you type. • The layout of the editor elements is based on a tree-based graph layout that only works with constrains (no actual visible edges between the editor elements). • The editor works live, so adding new elements to the scene properly rearranges the scene. • But, perhaps, the most exciting part is the fact that the lines connect an element from inside the text editor element with another that lives outside of the editor element. All these validate the architecture of Bloc of having exactly one rendering tree. It was not an obvious goal a couple of years ago, but we are really happy that it works. To put it in perspective, let's compare this with the html world. Text is text is rendered through the DOM tree. If you want graphics you might use something like SVG which comes with its own tree. However, these are two distinct worlds, and you cannot go from one to another, or at least not easily. This is the case in most engines we looked at. Why is this important? One thing we learn in the Smalltalk world is that covering the same space with less concepts opens up a whole dimension of creativity that is simply not possible outside of it. The goal with Bloc is to enable new kinds of user interfaces. As we are late to the game of modern interfaces, even though the field was invented in Smalltalk, our only chance to take the lead again is to rethink the model. Let's look at the Connector again. In most user interfaces we have panes on the outside, and visuals confined within the boundaries of those panes. Interestingly, we can trace this pattern to the very first Smalltalk interfaces. In the Connector interface we have no boundaries with text and visualization being intertwined to form a new kind of workflow. Talking about workflows, we now have two distinct and novel ways to explore examples: one is Connector, and the other one is the expandable code editor. For example, the scene from above looks like this in the example expanding editor: Both of these interfaces are not found in other infrastructures, and yet they were both inexpensive to implement in Bloc. We believe this will have a deep impact for all sorts of interfaces, and especially for the IDE. If you are interested in more details related to the IDE, take a look at the following paper from 2015: http://scg.unibe.ch/archive/papers/Girb15b-PervasiveSoftwareVisualizations.… Please let us know what you think. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

6 years, 11 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