- Moose-dev - INF Mailman

MalNode that store their neighbors nodes

by Serge Stinckwich

Hi all, I'm using MalGraphAlgorithm to build simulations of disease propagation on random network and for performance reason, I need to store inside each nodes of my network, the neigbours nodes. I see a class MalNodeWithNext that store next edges, is it the class I should use for my nodes ? I see a trait called #MalTEdgeNode, is it related ? how it works ? Thank you. Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

7 years, 10 months

1
0
0 0

Zeroconf to execute playground in a pre-made image (winddows 10)?

by Cris Fuhrman

Hello all, I have a playground script that will analyze the first MSE model and produces output in a CSV file. I would now like to be able automate this, and I think Tudor Girba gave me a hint of using Zeroconf. So far I have not been able to get it to work under Windows 10. The curl command works to get the image from get.pharo.org, curl get.pharo.org | bash However, the following attempts don't result in errors, but I don't get any useful output either: $ bash ./pharo Pharo.image --help $ ./pharo Pharo.image --help $ pharo-vm/PharoConsole.exe --headless Pharo.image --version Does it work in Windows 10? I've tried in Git Bash and CMD.exe (the last command, since the bash commands don't work). Cheers, C. Fuhrman

7 years, 10 months

1
1
0 0

Generating GTInspector extension screenshots?

by Luke Gorrie

I have built an application based on the GTInspector. Hurray! Now I want to share it and I need to write documentation. I would like to include screenshots in the docs but I don't want to create them by hand. So my question is: Is there an easy way to automatically generate screenshots for GTInspector extension methods? e.g. to specify an object and the name of a presentation and to get a PNG file of how that looks in the GTInspector. Thanks! P.S. References to how other people write their docs in general would be interesting. P.P.S. Here is GTInspector browsing internal data structures of a JIT compiler :-)

7 years, 10 months

5
10
0 0

[ann] moldable brick editor - alpha

by Tudor Girba

Hi, We are very happy to announce the alpha version of a moldable editor built in Brick (https://github.com/pharo-graphics/Brick) which is based on Bloc (https://github.com/pharo-graphics/Bloc). This is primarily the work of Alex Syrel. The project was initially financially sponsored by ESUG and it is currently supported by feenk. And of course, the project is based on the tremendous work that went into Bloc and Brick by all contributors. Take a look at this 2 min video: https://www.youtube.com/watch?v=2vy6VMJM9W4&feature=youtu.be The basic editor works and it is both flexible and scalable. For example, the last example shown in the video is an editor opened on 1M characters, which is reasonably large, and as can be seen see one can interact with it as smoothly as with the one screen text. It actually works just as fine with 100M characters. The functionality of the editor includes: rendering, line wrapping, keypress and shortcut handling, navigation, selection and text styling. Currently, the editor is 1260 lines of code including method and class comments. This is not large for a text editor and this is possible because most of the work is done by generic concepts that already exist in Bloc such as layouts and text measurements. Beside the small maintenance cost, the benefit is that we have the option to build all sorts of variations with little effort. That is why we call this a moldable text editor. Another benefit of using elements and layouts is that we can also embed other kinds of non-text elements with little effort (such as pictures), and obtain a rich and live text editor. We already have basic examples for this behavior, and we will focus more in the next period on this area. The next immediate step is to add syntax highlighting. Beside the text attributes problem, this issue will also exercise the thread-safety the implementation is. The underlying structure (https://en.wikipedia.org/wiki/Rope_(data_structure)) is theoretically thread-safe, but it still needs to be proven in practice. We think this is a significant step because the editor was the main piece missing in Brick and it will finally allow us to build value that can be directly perceived by regular users on top of Brick and this, in turn, will generate more traction. Please also note that because now Bloc is directly embeddable in Morphic it means that we can actually start using it right away. For example, the picture below shows the text element being shown through a live preview in the GTInspector. This is another puzzle piece towards the final goal of engineering the future of the Pharo user interface. There is still a long way to go to reach that goal, but considering the work that is behind us, that goal that looked so illusive when Alain and Stef initiated the Bloc project is now palpable. We will continue the work on this over the next period and we expect to announce new developments soon. If you want to play with it, you can load the code like this (works in both Pharo 6 and 7): Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'Brick'; repository: 'github://pharo-graphics/Brick/src'; load: #development Please let us know what you think. Cheers, Alex and Doru -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

7 years, 11 months

1
0
0 0

jenkins 32 bit nodes offline?

by Tudor Girba

Hi, The 32 bit nodes on Jenkins are offline and I cannot seem to be able to restart them. Does anyone have an idea of what is going on? Cheers, Doru -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them."

7 years, 11 months

1
2
0 0

Wrong containers?

by Pavel Krivanek

Hi, I was checking the containers in the current Famix and I have found several strange attributes: FAMIXSourceAnchor>>#element is container but the relationship to FAMIXSourcedEntity has one to one cardinality. It is the only case like this and it is probably wrong. Does it have any reason or is it an error? Then the relation between FAMIXSourcedEntity>>#containerFiles and FAMIXFile>>#entities it the only one with cardinality many to many where a container is specified but Vincent already told me that this is an error. Cheers, -- Pavel

7 years, 11 months

2
1
0 0

mondrian issue with nested elements and global edges

by Tudor Girba

Hi, I am trying to use Mondrian for a case in which I have nested elements and crosscutting edges. The issue is that I only found a cumbersome way to specify the layout. Here is an example: view := RTMondrian new. view shape rectangle fillColor: Color transparent. nodes := view nodes: { { 1 . 2 } . { 11 . 12 } } forEach: [ :col | view nodes: col ]. view edges source: { 1 . 11 } connectFrom: [ :x | x ] to: [ :x | x + 1 ]. view edges source: { 1 . 2 } connectFrom: [ :x | x ] to: [ :x | x + 10 ]. nodes do: [ :each | RTNest new layout: RTTreeLayout new; on: each nest: each nestedElements ]. view With bold I have showed the code necessary for applying the layout. In previous versions of Roassal/Mondrian, layouts were applied lazily, after the graph was constructed. This allowed us to write something like this: view := RTMondrian new. view shape rectangle fillColor: Color transparent. view nodes: { { 1 . 2 } . { 11 . 12 } } forEach: [ :col | view nodes: col. view layout tree ]. view edges source: { 1 . 11 } connectFrom: [ :x | x ] to: [ :x | x + 1 ]. view edges source: { 1 . 2 } connectFrom: [ :x | x ] to: [ :x | x + 10 ]. view Did I miss something or is this the only way supported currently? Cheers, Doru -- www.tudorgirba.com www.feenk.com "To utilize feedback, you first have to acquire it."

7 years, 11 months

2
7
0 0

Roassal histogram bars left shifted

by Hernán Morales Durand

Hi guys, I am experiencing a problem visualizing histograms in Roassal with Pharo 5. In the attached image you can observe the first bar shape starts from a negative X axis value, where I want to start from 0. Besides, some bars are gapped but I don't know why. I am using with the following code: | bins minPoint g ds | bins := self groupedBySeqLengthDistribution: binNumber. minPoint := ((bins reject: #isEmpty) detectMin: [ : c | c size ]) anyOne size. " Build diagram " g := RTGrapher new extent: 500 @ 200; minX: minPoint; withoutOrigin; yourself. ds := RTData new points: bins; x: [ : c | c ifEmpty: [ minPoint ] ifNotEmpty: [ : d | d anyOne size ] ]; y: #size. ds barShape borderColor: Color black; color: aColor; width: barWidth. g add: ds. " Configure axis settings " g axisY title: axixYLabel; color: Color black; noDecimal. g axisX noDecimal; fromPoint: minPoint; color: Color black; title: axisXLabel. " Open visualization in a new window " g open. Any idea what I am missing? Cheers, Hernán

7 years, 11 months

3
12
0 0

Questions about building a custom playground-like browser

by Luke Gorrie

Howdy! I want to build a Playground-like browser and I'd really like some help for getting the initial prototype up and running. I see two parts: - Code entry with "Go" button. - Code execution with output printed (interpreter running as unix process.) I have made a start on the "Code entry" pane like this: | composite | composite := GLMCompositePresentation new. composite title: 'Script editor'. composite text. composite act: [] iconName: #glamorousGo on: $G entitled: 'Run'. composite openOn: ''. which does look the way that I want: but the part I am missing is how to make the "Go" action (green arrow) cause a new object to be inspected in a miller column to the right (like in the Playground and the Inspector.) Could somebody please tell me how to update the example to make this happen? The next part is that I want to run the code using an interpreter running in a separate unix process (a PipeableOSProcess.) I have made a GTInspector extension to inspect this process and show its output, but I am looking for a way to automatically refresh the presentation when new output becomes available (e.g. polling at ~100ms interval and inserting new text that has been printed.) Can somebody give me a hint about how to update that presentation with the latest output of the process? Then, once the code has finished running, I want to refresh the inspector with potentially some new views based on the final result. But I would be more than satisfied to just solve the first two issues for now :-) Thanks in advance! I have read the masters thesis on Glamour and I feel like I am slowly developing a mental model but it's not all there yet. To guess it seems like I need to embed my GLMCompositePresentation into a browser based on miller-columns and to somehow send my new object to its #selection port. Or something like that...

7 years, 11 months

3
17
0 0

moose jenkins status

by Andrei Chis

Hi, Are the moose jenkin servers back on? While they seem to be back on I get a lot of 'Service Temporarily Unavailable', can't start new builds and cannot download previously built images. Cheers, Andrei

7 years, 11 months

1
0
0 0

Glamour accordion presentation

by Peter Uhnák

Hi, I'm playing around with Glamour and accordion presentation, however there are couple things I'm struggling with. I have a simple presentation: ``` | browser data| data := { 'First' -> #(1 2 3). 'Second' -> #(a b c). 'Third' -> #(A B C). 'Fourth' -> #(! @ #'#'). }. browser := GLMTabulator new. browser column: #accordion. browser transmit to: #accordion; andShow: [ :a | a accordionArrangement. a title: 'Accordion'. data do: [ :pair | a fastList title: pair key; display: pair value ]. a list. ]. browser openOn: #(). ``` * Is it possible to tell the accordion to not take more space than is needed? E.g. after item 3, and after item $c there's lot of empty space. * Is it possible to close accordions upwards? I have added an empty list at the end to consume extra white space, but it is insufficient (see point above) and ugly. * Is it possible to control which accordions are opened/closed by default? * Is it possible to connect all the lists so only one item can be selected at any time? Currently I can select independently in the lists. * Is it possible to build the lists from the input data (=openOn: XXX)? I can fill the data, but if I am making multiple lists then I am lost. (I could use tree to fix most of the problems, but Accordion looks much nicer :)) Any pointers appreciated, Peter

7 years, 12 months

2
1
0 0

XMI-Analyzer update

by Hernán Morales Durand

Hi Usman and others, I am trying to visualize an UML diagram using a XMI file in Moose. The attached file contains some updates to load properly using the latest XML-Parser in Moose 6: XMLDOMVisitor -> XMLNodeVisitor #visit: -> #visitDocument: Feel free to integrate into your repo if you like. Cheers, Hernán

8 years

2
4
0 0

Packaging issue on MooseTechnology

by Anne Etien

Hi, If you want to download the last image from MooseTechnology, on a linux, the associated VM is not the right one, so there is an issue when you open the Metabrowser. The issue is solved when you download the T60 VM. Can someone well packaged the image or just change the link on MooseTechnology? Thanks in advance Anne

8 years

2
2
0 0

CFP - IWST 2017 - International Workshop on Smalltalk Technologies - Kind reminder

by Anne Etien

Kind reminder. New deadlines of June 16th for abstract and June 21st for papers are firm!! Cheers, Jannik and Anne > Début du message réexpédié : > > De: Anne Etien <anne.etien(a)univ-lille1.fr> > Objet: [Esug-list] CFP - IWST 2017 - International Workshop on Smalltalk Technologies - Extension deadline > Date: 12 juin 2017 10:59:52 UTC+2 > À: esug-list(a)lists.esug.org > > Dear Smalltakers, > > Deadline of IWST has been postponed to June 21th AoE. > However, we ask you to submit at least an abstract for June 16th. Only papers submitted before this date could be modified until June 21th. > > Thanks in advance, > Cheers, > > Jannik and Anne > > >> Début du message réexpédié : >> >> De: <jannik.laval(a)gmail.com <mailto:jannik.laval@gmail.com>> >> Objet: [Moose-dev] CFP - IWST 2017 - International Workshop on Smalltalk Technologies >> Date: 13 avril 2017 10:59:00 UTC+2 >> À: "'Moose-related development'" <moose-dev(a)list.inf.unibe.ch <mailto:moose-dev@list.inf.unibe.ch>> >> Répondre à: Moose-related development <moose-dev(a)list.inf.unibe.ch <mailto:moose-dev@list.inf.unibe.ch>> >> >> CFP - IWST 2017 - International Workshop on Smalltalk Technologies >> >> [Please accept our apologies if you receive multiple copies of this call] >> [Please send to interested colleagues / mailing-lists] >> ************************************************************************************************************ >> CALL FOR PAPERS >> >> IWST 2017 — International Workshop on Smalltalk Technologies >> http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_… <http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_…> >> >> Maribor, Slovenia; Between September 4th to 8th, 2017 >> ************************************************************************************************************ >> >> ------------------- >> 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 16th, 2017 >> Notification deadline: July 21th, 2017 >> Workshop : between September 4th and 8th, 2017 >> All accepted papers will be published in ACM DL (To be confirmed) >> >> ------------------- >> 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 illegible, 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.acm.org/sigs/sigplan/authorInformation.htm <http://www.acm.org/sigs/sigplan/authorInformation.htm>. 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=iwst2017 <https://easychair.org/conferences/?conf=iwst2017> >> >> ------------------- >> Program chairs >> ------------------- >> Anne Etien (Université de Lille 1, France) >> Jannik Laval (Université Lyon 2 Lumière, France) >> >> >> -- >> ~~Jannik Laval~~ >> Enseignant-chercheur >> Responsable Pédagogique Licence Coordonnateur de Projet en Système d'Information >> IUT Lumière <http://iut.univ-lyon2.fr/>, Université Lumière Lyon 2 <http://www.univ-lyon2.fr/> >> laboratoire DISP <http://disp-lab.fr/> >> +33 4 78 77 43 06 >> http://www.jannik-laval.eu <http://www.jannik-laval.eu/> >> http://www.phratch.com <http://www.phratch.com/> >> http://www.approchealpes.info <http://www.approchealpes.info/> >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <x-msg://221/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >> https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

8 years

1
0
0 0

[ANN] x64 Moose Image

by Blondeau Vincent

Hi, I am happy to announce that there is a Moose image that is now built for x64 VMs. It allows to increase the memory limitation to load the models for Moose. Almost all the tests are passing, but there are some random seg faults that occurred during some previous builds... So it is not yet stable. All is here: https://ci.inria.fr/moose/job/moose-6.1-x64/. Of course, you need the x64 VM to run the image;) I consequently added a x64 slave to run the jobs. Others jobs should be restricted to x32 images (label "32") (I migrated almost all of them): [cid:image004.png@01D2E389.622AC300] Have fun! Cheers, Vincent !!!************************************************************************************* "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.!!!"

8 years

2
1
0 0

Pharo 6.0 crashes a lot (so far) on my windows 10

by Cris Fuhrman

Hi all, I started a new visualisation project using the latest moose image and Pharo 6.0. Unfortunately, I have been experiencing a lot of crashes in RTMondrian after importing CSV files with neocsv. They are Windows 10 crashes, where Windows tells you that pharo has crashed, sometimes when I run a program, sometimes when I return to the Pharo vm after browsing a web page. I have started over my project image a few times already, since I suspect the corruption of memory remains in the VM. I'm wondering how to find out more information about why the crash is occurring, so I can provide info to the Pharo or Moose teams. The debug log that I found in the folder where I have the images just refers to errors in my Pharo code. How can I find more information about the crashes? What environment is most stable for Pharo 6? OSX, Linux? I wondered since there are no 64-bit VMs for Windows. I tried to go back to Pharo 5, but neocsv complains it was not tested for it, so I didn't pursue that option. I like the new dark look! Cheers, C. Fuhrman

8 years

2
3
0 0

CFP - IWST 2017 - International Workshop on Smalltalk Technologies

by jannik.laval＠gmail.com

CFP - IWST 2017 - International Workshop on Smalltalk Technologies [Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] **************************************************************************** ******************************** CALL FOR PAPERS IWST 2017 International Workshop on Smalltalk Technologies http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_1 7 Maribor, Slovenia; Between September 4th to 8th, 2017 **************************************************************************** ******************************** ------------------- 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 16th, 2017 Notification deadline: July 21th, 2017 Workshop : between September 4th and 8th, 2017 All accepted papers will be published in ACM DL (To be confirmed) ------------------- 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 illegible, 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.acm.org/sigs/sigplan/authorInformation.htm. 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=iwst2017 ------------------- Program chairs ------------------- Anne Etien (Université de Lille 1, France) Jannik Laval (Université Lyon 2 Lumière, France) -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet en Système d'Information <http://iut.univ-lyon2.fr/> IUT Lumière, <http://www.univ-lyon2.fr/> Université Lumière Lyon 2 <http://disp-lab.fr/> laboratoire DISP +33 4 78 77 43 06 <http://www.jannik-laval.eu/> http://www.jannik-laval.eu <http://www.phratch.com/> http://www.phratch.com <http://www.approchealpes.info/> http://www.approchealpes.info --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

8 years

2
2
0 0

QueryCache and PropertyCache in MooseState

by Cyril Ferlicot D.

Hello, I asked a question on Discord bug I got no answer. Maybe I will have more arswer here. The moose state has three different caches: - attributes - property cache - query cache I know that the attribute cache is a cache that is rarely cleared. But what is the difference between the propertyCache and the queryCache? Could we not just use the propertyCache all the time? -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

8 years

1
0
0 0

Re: dynamic interaction with Mondriam

by Blondeau Vincent

Hi, You should ask in the Moose list ;) Vincent > -----Message d'origine----- > De : Alidra Abdelghani [mailto:alidrandco@yahoo.fr] > Envoyé : mercredi 7 juin 2017 15:34 > À : pharo-users(a)lists.pharo.org > Objet : dynamic interaction with Mondriam > > Hi all, > > I would like to do some visualisations with Mondrian where you change the > visualisation by selecting actions. For instance you have : > b := RTMondrian new. > b shape rectangle withTextAbove. > b nodes:(1 to: 5). > b layout grid. > b edges connectFrom: [ :e | e + 1 ]. > b build. > b view > > then you can click a button to: > 1 display/hide the labels above the elements. > 2 display/hide some elements (all odd numbers for instance) > 3 display/hide connections between elements. > I saw a visualisation in the Roassal examples where you can add elements in a > dynamic stack grapher. So I presume it is possible to do the same with other > types of visus. > > Any hints? > Thanks in advance. > Abdelghani !!!************************************************************************************* "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.!!!"

8 years

4
5
0 0

bug in layered tree

by Tudor Girba

Hi, Take a look at this script: http://ws.stfx.eu/54G9IO1XX4R2 It produces this. The issue is that instead of aligning the top left, it kind of centers the entities from the same layer: This used to work properly, and the tree algorithm did not change. So something must have changed not too long ago related to translations. Does anyone have a better idea of where this could come from? Cheers, Doru -- www.tudorgirba.com www.feenk.com "From an abstract enough point of view, any two things are similar."

8 years

2
3
0 0

preparing for 6.1

by Tudor Girba

Hi, Now that Pharo 6.0 was released, I want to prepare for the Moose 6.1 release. I went through most of the issues and closed half of them. We still have some 78 total issues open. I marked some that I find important for the release here: https://github.com/moosetechnology/Moose/milestone/2 Please take a look at the issue tracker and feel free to add the 6.1 milestone to them. Cheers, Doru -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

8 years

1
0
0 0

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

8 years

2
3
0 0

[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>

8 years

1
0
0 0

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

8 years

2
3
0 0

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

8 years, 1 month

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