_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
On Fri, Mar 3, 2017 at 2:34 PM, said yebbah <[hidden email]> wrote:
> Hello, Bonjour, > We‘re a group of 3 students from a course with Stéphane Ducasse in > university of Lille 1, > and we’re beginners in Pharo and for the next 2 weeks we have to work on an > open source project. > we choose Roassal project. So we would like to know what's the prupose of > ideas that we've to do ? > In fact, in the moments we're at the point of discovering Roassal. Welcome in the community ! I have one idea for a small project for students. I give this link to my students for a lecture at Paris 6 University, is it possible to do the same with Roassal: https://github.com/SergeStinckwich/ARE-UPMC/blob/master/ARE-DYNAMIC/fiche3.ipynb and if not how you fix that ? Thank you. -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by said yebbah
This is better to answer on the mailing-list. Regards, On Fri, Mar 3, 2017 at 3:30 PM, said yebbah <[hidden email]> wrote:
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by said yebbah
Hi, welcome to the community. While you are discovering Roassal, can you try to memorize moments where something didn’t work just because you didn’t know a simple rule? For example if you specify edges in a graph wilder before specifying nodes, the edges will not be added. To help people with this kind of problems I created a rule that detects if the “edges:” message is sent before the “nodes:” message, and warns about it. If you come up with more issue like the one I described, your project can be also to add Roassal-speciffec rules that help users to avoid mistakes while using Roassal. Cheers. Uko
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by said yebbah
Hi Said,
There are plenty of possible topics around Roassal. Having a playground dedicated to Roassal (with a smart auto-completion and highlight) is one excellent topic. But I am not sure how difficult is it. Another topic is a new interaction engine. Currently, most of the interaction happens with GTInspector. But it is limited in several aspects (linear flow, lake of context to carry on across panes). Best is to join the slack channel and discuss Cheers, Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Free forum by Nabble | Edit this page |