Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

eyesee presentation vs graphET presentation

by Fabrizio Perin

Hi, I built sometimes ago a tab in the moose panel to show an eyesee pieChart: *viewAccessesTypesPieChartIn: composite <moosePresentationOrder: 275> composite eyesee title: 'Database accessor types'; titleIcon: MooseJEEIcons pieChart; diagram: [ :view :each | each mooseInterestingEntity viewAccessesTypesPieChartOn: view ]; when: [ :input | input mooseInterestingEntity isKindOf: FAMIXDBAccessGroup ]* Now, if I load eyesee and the eyesee glamour presentation everything is fine, however, I would like to port this view on graphET. So, I tried: *viewAccessesTypesPieChartIn: composite <moosePresentationOrder: 275> composite graphET title: 'Database accessor types'; titleIcon: MooseJEEIcons pieChart; diagram: [ :view :each | each mooseInterestingEntity viewAccessesTypesPieChartOn: view ]; when: [ :input | input mooseInterestingEntity isKindOf: FAMIXDBAccessGroup ]* now the local variable *each *contains the presentation instead of the model, is that a wanted feature? If so, how can i access the model elements to invoke the view I need? Should I move the logic that implements the view? Thanks in advance, Fabrizio

10 years, 10 months

Re: How to show graphs from the Moose panel?

by Blondeau Vincent

Hi, Yes by graph I mean curves. I used GraphET to compare some curves at the same time because Charter is very low level for what I want, and EyeSee is not loaded in Moose. So with GraphET and 2 or 3 curves that's manageable. But if I want to do a graph like that, with 10 curves: [cid:image002.png@01CFAC20.5B911740] How can I retrieve the names of the curves? Automatic colors and legend? Popups? Thanks in advance. Cheers, Vincent Blondeau -----Message d'origine----- De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de Alexandre Bergel Envoyé : jeudi 24 juillet 2014 18:38 À : Moose-related development Objet : [Moose-dev] Re: How to show graphs from the Moose panel? What do you mean by graph? Simple curve? You can use EyeSee or GraphET2. I have recently started to work on Charter, a Roassal builder to draw graph. You can try it: -=-=-=-=-=-=-=-=-=-=-=-= | b | b := RTCharterBuilder new. b extent: 400 @ 400. b shape ellipse color: (Color blue alpha: 0.5). b points: (0.0 to: 1.0 by: 0.05). b curve. b y: [ :v | v sqrt ]. b axisXWithNumberOfTicks: 3. b axisYWithNumberOfTicks: 4. b open. -=-=-=-=-=-=-=-=-=-=-=-= If you have particular request for Charter, we will implement them. Charter is still very raw... Alexandre On Jul 24, 2014, at 11:15 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: > Hello everyone, > > In a former moose version, it was being able to do on a MooseGroup : Browse>>In Eye See Editor. > Now it is not possible... > > What tool should I use to draw graphs? > > 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. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch<mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch<mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev ________________________________ 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.

10 years, 10 months

SVG-described icons

by Alexandre Bergel

Hi! We fixed some bugs in the way path were rendered. Path can now be scaled and answer properly to events. You can register callbacks or other kind of interaction you wish. Here is a screenshot: This code is available from: RTRoassalExample>>exampleSVGPath Icons have been obtained from http://iconmonstr.com Thanks Juraj of the improvement you’ve made to TRSVGPath ! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 10 months

print it in GTInspector

by Alexandre Bergel

Hi! There is a behavior that does not match my way of printing expressions. 1 - open a playground 2 - enter: 10 3 - print it (cmd-p) 4 - remove what has been printed by pressing backspace 5 - the value 10 is selected, which is a problem to me. Would it make sense to have the 10 unselected at that point? I do not see what could the reason to have it selected. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 10 months

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

by admin＠moosetechnology.org

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

10 years, 10 months

Edge driven layout on groups - bug and correction

by Usman Bhatti

Hi, We spotted a bug related to edge driven layouts and groups. So, when a view has groups in it, performing an edge driven layout gives MNU: RTGroup>>view. The bug can be reproduced with the following script in latest Roassal. view := RTView new. group1 := RTGroup new add: (RTBox new elementOn: 1); yourself. group2 := RTGroup new add: (RTEllipse new elementOn: 2); yourself. view addAll: group1; addAll: group2. RTForceBasedLayout on: (RTGroup with: group1 with: group2). view open The link to get the version with changes (because problem posting more than 1 mb on this list): https://dl.dropboxusercontent.com/u/11804892/Roassal2-usmanbhatti.416.mcz All tests are green after the change. Alex, can you integrate this in Roassal because it is important for our work. tx, Usman & Leo

10 years, 10 months

Updating the list of users

by Alexandre Bergel

Hi! We try to keep track of users of Roassal. It would be great to have your logo on http://objectprofile.com/Users.html So, if you are a Roassal (or Hapao, Roassal3d, Spy) user, let us know please! It helps building a strong community. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 10 months

[Solved] Pharo image corruption and fatal VM error with Roassal

by Blondeau Vincent

Solved ! You will found the changes in the attached .mcz. I added some sessions guards where some Athens external objects are used. Stef you were right ;) Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path that relies on Athens external objects. It seems to works for me. If it is the case for you, it we be nice to integrate it quickly to be able to work fine :) Thanks Vincent -----Message d'origine----- De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de stepharo Envoyé : jeudi 31 juillet 2014 22:58 À : Pharo Development List Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error with Roassal Alexandre may be you should try to understand what is a session. Because this is about 2 lines of code. When you open an image you save 2 min ago or 2 years ago, how the system knows that an OS ressources is valid? By checking the session id... Stef On 31/7/14 16:09, Alexandre Bergel wrote: > Yes, and this is a mess. > I've spent quite some time in getting the session working with Roassal2 and it still does not work. I would appreciate help on this. > > Alexandre > > > On Jul 31, 2014, at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> It looks like Trachel does not recreate athens external resources. >> There is an example in AthensSceneView, on how to check and reload an >> AthensSurface. >> >> >> 2014-07-31 12:51 GMT+02:00 Usman Bhatti <usman.bhatti(a)gmail.com>: >> >> >> >> On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: >> Yes it is. But I will not do >> >> TRMorph allInstances do: #delete >> >> In command line every day... >> >> >> It is only intended to recover your lost work in the image not for everyday use :). >> >> >> >> >> 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> 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 : >> >> <image001.png> >> >> 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: >> >> <image002.png> >> >> >> >> 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. >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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.

10 years, 10 months

Roassal now support Double clicks

by Alexandre Bergel

Hi! Leo, double clicks have been added to Roassal :-) -=-=-=-=-=-=-=-=-= | v es | v := RTView new. es := (RTBox new color: Color purple; size: 25) elementsOn: (1 to: 100). es when: TRMouseDoubleClick do: [ :e | e element trachelShape color: Color red. v signalUpdate ]. v addAll: es. RTGridLayout on: v elements. v open. -=-=-=-=-=-=-=-=-= This is a contribution from Juan-Pablo Sandoval Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 10 months

support for multiple file anchors in Famix

by Usman Bhatti

Name: Famix-SourceAnchor-usmanbhatti.44 Author: usmanbhatti Time: 8 August 2014, 3:43:01.966938 pm UUID: 2e5e4d96-f927-4a96-9b6e-e8f0e1507eae Ancestors: Famix-SourceAnchor-VincentBlondeau.43 adding FAMIXMultiFileAnchor, a source anchor for entities defined in multiple files. It has a collection of FAMIXFileAnchor objects which point to the individual definition files. It makes sure not to duplicate FAMIXFileAnchor with similar names/paths to optimize memory. SourceText returns the string of all FileAnchor contents with a separator line between them. To create, Use FAMIXSourcedEntity>>defineMultiSourceAnchorWithPath:. See tests. Name: Famix-Tests-Core-usmanbhatti.46 Author: usmanbhatti Time: 8 August 2014, 3:45:48.287238 pm UUID: 18bdabf9-815a-49b4-b0bd-7716f1220436 Ancestors: Famix-Tests-Core-TudorGirba.45 adding tests for multiple file anchor. ====================== Moose build is as unstable at it was before this change.

10 years, 10 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