Moose-dev July 2014

moose-dev@list.inf.unibe.ch

36 participants
143 discussions

by Alexandre Bergel

Hi! If I put the mouse above the play icon, top right of a window. The keybinding (cmd-o) may be indicated no? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

Charting library...

by Alexandre Bergel

Hi! Just to share the progress of the new charting library we are working on. Accessible from the Roassal example World menu entry Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal

by Blondeau Vincent

Yes it is. But I will not do TRMorph allInstances do: #delete In command line every day… Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Usman Bhatti Envoyé : jeudi 31 juillet 2014 10:59 À : Pharo Development List Cc : Moose-related development Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal This may be related to this known issue reported a few days back. https://code.google.com/p/moose-technology/issues/detail?id=1084 And there is a possible solution to recover your image. usman On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi, Yesterday, I was using GraphET (a part of Roassal) to do some charts and, today, when I wanted to reopen the image. And I got that : [cid:image001.png@01CFACAF.C4370C70] It is *very* unpleasant… To reproduce the bug: 1 - You can do either: | builder | builder := GET2Line data: (0 to: 100) . builder y: [ :x | x*x ]. builder open. Or WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph should be opened. 2 - don’t close the graph and save the pharo image. 3 – Close the pharo image 4 - Reopen it I am under W7 x64 with the latest moose image and the VM available on the pharo.org<http://pharo.org> website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july. You will find the crash dump attached. Thankfully, I managed to open the image with a latest VM (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip). Thanks a lot Eliot ! :) And I got this: [cid:image002.png@01CFACAF.C4370C70] Thanks in advance Cheers, Vincent BLONDEAU ________________________________ 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. ________________________________ 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.

9 years, 8 months

Telescope Beta - An API to create and customize interactive visualizations

by Leo Perard

Hi all, I am please to present you Telescope. Telescope provides a system to express highly interactive software visualizations and a rich API to express interactive, dynamic, and customized visualizations built on top of Roassal. You can find more information and tutorials here. Telescope is almost finish (missing some tests, little features...) and now it needs your feedback. To install Telescope Gofer new smalltalkhubUser: 'LeoPerard' project: 'Telescope'; package: 'ConfigurationOfTelescope'; load. (Smalltalk at: #ConfigurationOfTelescope) load A small example to get a tree explorer | visualization | visualization := TLTreeExplorer new root: Collection; property: #subclasses; yourself. visualization nodeBuilder shapeBuilder: TLEllipseShapeBuilder new. visualization nodeBuilder nodeLabel: #name position: #inside. visualization nodeBuilder addInteraction: TLNodeBasicInteraction popup. visualization nodeBuilder addInteraction: TLNodeBasicInteraction draggable. visualization open In this visualization, click on the blue circle to expand the node and the red to collapse it. In the class TLDemos you can find others examples to understand how it works. -- Cheers, Leo Perard University of Lille 1

9 years, 8 months

Pharo image corruption and fatal VM error with Roassal

by Blondeau Vincent

Hi, Yesterday, I was using GraphET (a part of Roassal) to do some charts and, today, when I wanted to reopen the image. And I got that : [cid:image001.png@01CFACAA.E0CB2060] It is *very* unpleasant... To reproduce the bug: 1 - You can do either: | builder | builder := GET2Line data: (0 to: 100) . builder y: [ :x | x*x ]. builder open. Or WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph should be opened. 2 - don't close the graph and save the pharo image. 3 - Close the pharo image 4 - Reopen it I am under W7 x64 with the latest moose image and the VM available on the pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july. You will find the crash dump attached. Thankfully, I managed to open the image with a latest VM (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip). Thanks a lot Eliot ! :) And I got this: [cid:image002.png@01CFACAD.350D7DB0] Thanks in advance Cheers, Vincent BLONDEAU ________________________________ 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.

9 years, 8 months

Workspace vs playground. Which name to use?

by Alexandre Bergel

Hi! The World menu contains the entry Workspace. Clicking on it open a playground. Maybe we could unify this and pick just one name? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

Jenkins build is back to stable : moose-5.0 #2017

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/2017/>

9 years, 8 months

Re: [Pharo-users] Roassal2 orthogonal lines, attach points and self-lines.

by Alexandre Bergel

Hi Peter! I’ve just added the orthogonal vertical and horizontal lines in Roassal2. Here are some screenshots. These last script has been made with: -=-=-=-=-=-=-=-=-=-=-=-= | v | v := RTView new. v addAll: ((RTEllipse new size: 20; color: (Color red alpha: 0.3)) elementsOn: (1 to: 20)). shape := RTMultiLine new. shape orthoVertical. shape color: (Color blue alpha: 0.3). RTEdge buildEdgesFromObjects: (1 to: 20) from: [ :n | n // 3 ] to: #yourself using: shape inView: v. v elements @ RTDraggable @ RTPopup. RTTreeLayout on: v elements. v open -=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jul 26, 2014, at 3:57 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote: > Hi, > > is there any support for orthogonal lines in Roassal2? I've seen something similar (ROOrthoVerticalLineShape), however nothing of that sort in Roassal2. I would imagine it to behave similarly to RTBezierLine - having controllingElements to specify the corners. (While ROOrtholines did it automatically I was looking for something more manual, so it can go in both directions - thus the controllingElements). > > Second thing I wasn't able to figure out is whether it is possible to create line from element to itself. All *AttachPoint classes aren't really able to cope with that. The best result I got was from Vertical/Horizontal AttachPoints (combined with BezierLine), however I would like to be able to specify which side it would start on and end on. Ideally not just middle of sides, but arbitrary part of the shape (I imagine that might be hard for non-rectangular shapes). > > Thanks, > Peter

9 years, 8 months

Build failed in Jenkins: moose-5.0 #2014

by admin＠moosetechnology.org

9 years, 8 months

Jenkins build became unstable: moose-5.0 #2011

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/2011/>

9 years, 8 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2014