Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

about graphEt
by Stéphane Ducasse 30 Jan '14

30 Jan '14

Hi daniel can you express the following graph with GraphEt Stef

3 6

SVG Icon in Roassal2
by Alexandre Bergel 30 Jan '14

30 Jan '14

Hi! Just to keep you updated with the excellent work Sergio Maas did with Roassal 2. Roassal2 now support SVG path. The cool thing about it, is that the web is stuffed with really nice looking icon (e.g., http://iconmonstr.com). We can now embed these icons in any visualization. As an example, consider this: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | v shape | v := RTView new. shape := RTSVGPath new path: 'M442.264,283.033l-90.66,52.343l28.787,16.621c-28.083,38.277-64.824,62.301-104.362,68.397V231.153 c0-54.82,48.786-60.084,48.786-112.339C324.814,80.869,293.944,50,256,50c-37.943,0-68.814,30.869-68.814,68.814 c0,52.694,48.786,57.052,48.786,112.338v189.242c-39.538-6.097-76.278-30.12-104.363-68.397l28.788-16.621l-90.66-52.343v104.686 l27.018-15.6C137.32,429.445,194.595,462,256,462s118.68-32.555,159.246-89.881l27.018,15.6V283.033z M227.242,118.814 c0-15.857,12.9-28.758,28.758-28.758c15.856,0,28.758,12.9,28.758,28.758c0,15.856-12.901,28.757-28.758,28.757 C240.143,147.571,227.242,134.671,227.242,118.814z'. shape fillColor: Color red. shape scale: [:vv | vv model ]. v add: ((shape elementsOn: #(0.1 0.2 0.3 0.4) ) @ RTPopup). v open -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

Jenkins build is back to stable : moose-5.0 #636
by admin＠moosetechnology.org 30 Jan '14

30 Jan '14

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

3 2

Re: [Roassal]Text on edges ?
by Alexandre Bergel 30 Jan '14

30 Jan '14

The problem here is that you are mixing Mondrian code and Roassal code. It is like putting some C or Assembly code in your Java code. You can do it, but you need to know exactly what’s going on. Without Mondrian, you can have: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | v e1 e2 l lbl | v := ROView new. e1 := (ROBox new size: 30) element. e2 := (ROBox new size: 30) element. l := ROLine elementFrom: e1 to: e2. lbl := (ROLabel text: 'hello world') element. ROConstraint stick: lbl between: e1 and: e2. "locate the label between 2 nodes" e1 @ RODraggable. e2 @ RODraggable. v add: e1; add: e2; add: l; add: lbl. v open -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If you really wish to stick to Mondrian, you can do: -=-=-=-=-=-=-=-= | b | b:= ROMondrianViewBuilder new. b shape circle size: 30. b nodes: #(1 2). b edgeFromAssociation: 1 -> 2. b open. b view edges do: [ :edge | | lbl | lbl := (ROLabel text: 'hello world') element. b view add: lbl. ROConstraint stick: lbl between: edge from and: edge to. ]. -=-=-=-=-=-=-=-= Cheers, Alexandre On Jan 30, 2014, at 6:51 AM, Vincent Blondeau <vincent.blondeau(a)polytech-lille.net> wrote: > Le 29/01/2014 11:49, Alexandre Bergel a écrit : >> Vincent, did it work? > Not really... > > The code I use is : > > //Node and edges creation > ... > view shape label centeredLabel. > labelNode := view node: 'Hello'. "create the label I want between (it's for the example)" > ROConstraint stick: labelNode between: view edges first from and: view edges first to. "locate the label between 2 nodes" > view treeLayout. > view open > > A text "hello" is displayed but at the begining, the text is misplaced : > <Mail Attachment.txt> > If I move one of the nodes linked to the edge, the text moves to the right location (the picture at the bottom, shows what I want to do :) ) > <Mail Attachment.txt> > But the text doesn't stay on the edge but it's between the left sides of the nodes... > > <Mail Attachment.txt> > Do I use the right method and the right arguments ? > > Thanks for helping ! > > Vincent >> >> Alexandre >> >> >> >>> On 24 Jan 2014, at 07:11, Vincent Blondeau <vincent.blondeau(a)polytech-lille.net> >>> wrote: >>> >>> Hello, >>> >>> I use Roassal to visualize a FAST AST as a kind of UML diagram. >>> Each node on Roassal is a node of the AST and the edges shows the parent link. >>> That's work fine and it's very easy to do it ! Thanks ! >>> >>> But I would like to add some text on the edges to know what are the instance variables containing the children nodes. >>> >>> I saw the examples and there's not a such functionality. >>> >>> Is it possible to add it ? >>> >>> Cheers, >>> Vincent >>> _______________________________________________ >>> Moose-dev mailing list >>> >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> _______________________________________________ >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Roassal]Text on edges ?
by Vincent Blondeau 29 Jan '14

29 Jan '14

Hello, I use Roassal to visualize a FAST AST as a kind of UML diagram. Each node on Roassal is a node of the AST and the edges shows the parent link. That's work fine and it's very easy to do it ! Thanks ! But I would like to add some text on the edges to know what are the instance variables containing the children nodes. I saw the examples and there's not a such functionality. Is it possible to add it ? Cheers, Vincent

2 2

Build failed in Jenkins: moose-5.0 #592
by admin＠moosetechnology.org 29 Jan '14

29 Jan '14

2 30

roassal2 job sets the author
by Tudor Girba 29 Jan '14

29 Jan '14

The Roassal2 job now sets the author. The builds does not crash anymore, but there are 11 failing tests. Here is the new script: ---- wget --quiet -O - http://get.pharo.org/30+vm | bash ./pharo Pharo.image save $JOB_NAME REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main ./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2 --install=development ./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image saveAs: 'roassal-tests'" ./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*" mv ./pharo-vm/PharoV20.sources ./ zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources ---- Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

3 6

Re: Build failed in Jenkins: roassal2 #50
by Alexandre Bergel 27 Jan '14

27 Jan '14

Apparently, the author info is asked by NativeBoost… Can you set the author in the script? Alexandre On Jan 27, 2014, at 11:28 AM, admin(a)moosetechnology.org wrote: > See <https://ci.inria.fr/moose/job/roassal2/50/> > > ------------------------------------------ > [URLTrigger] A change within the response URL invocation (log) > Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/roassal2/ws/> > > Deleting project workspace... done > > [roassal2] $ /bin/sh -xe /tmp/hudson3888068938556909847.sh > + + bash > wget --quiet -O - http://get.pharo.org/30+vm > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > + ./pharo Pharo.image save roassal2 > + REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main > + ./pharo roassal2.image config http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main ConfigurationOfRoassal2 --install=development > [31m[33m > =============================================================================== > Notice: Installing ConfigurationOfRoassal2 development > =============================================================================== > [0m[0mInstalling ConfigurationOfRoassal2 development > > Loading dev of ConfigurationOfRoassal2... > Fetched -> Trachel-SamirSaleh.60 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Fetched -> Roassal2-JurajKubelka.94 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Loaded -> Trachel-SamirSaleh.60 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > Loaded -> Roassal2-JurajKubelka.94 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > ...finished dev+ ./pharo roassal2.image test --junit-xml-output Roassal2.*|Trachel.* > [31m[33m > =============================================================================== > Notice: Running tests in 2 Packages > =============================================================================== > [0m[0mRunning tests in 2 Packages > [31mAn attempt to use interactive tools detected, while in non-interactive mode > Interactive Request: [ Author identification ] Please type your full name. > It will be used to sign the changes you make to the image. > Spaces, accents, dashes, underscore and similar characters are not allowed > > [0mNonInteractiveUIManager>>nonInteractiveWarning: > NonInteractiveUIManager>>nonInteractiveRequest:title: > NonInteractiveUIManager>>request:initialAnswer:title:entryCompletion: > NonInteractiveUIManager>>request:initialAnswer:title: > AuthorNameRequest>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > AuthorNameRequest(Exception)>>signal > Author>>requestFullName > Author>>fullName > Author class>>fullName > Author class>>changeStamp > SQSurfaceDispatch class(ClassDescription)>>compile:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: in Block: [ self compile: code classified: category notifyin...etc... > BlockClosure>>ensure: > SystemAnnouncer>>suspendAllWhile: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified: > SQSurfaceDispatch class(NBExternalStructure class)>>createAccessorsFor: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors in Block: [ :fldName | self createAccessorsFor: fldName ] > NBExternalStructureFields>>fieldNamesDo: in Block: [ :name | aBlock value: name ] > Dictionary>>keysDo: in Block: [ :association | aBlock value: association key ] > Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock value: each ] ] > Array(SequenceableCollection)>>do: > Dictionary>>associationsDo: > Dictionary>>keysDo: > NBExternalStructureFields>>fieldNamesDo: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors > SQSurfaceDispatch class(NBExternalStructure class)>>fields > [0mBuild step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Re: Issue 113 in moose-technology: Roassal should support lazy edges when used through the Mondrian API
by moose-technology＠googlecode.com 27 Jan '14

27 Jan '14

Updates: Summary: Roassal should support lazy edges when used through the Mondrian API Status: Labels: -Component-Mondrian Component-Roassal Comment #10 on issue 113 by tu...(a)tudorgirba.com: Roassal should support lazy edges when used through the Mondrian API http://code.google.com/p/moose-technology/issues/detail?id=113 No, it does not. But, it should. The idea is that the following Mondrian script should work: view edge: #edge from: 1 to: 2. view node: 1. view node: 2. For this, the edge creation should be evaluated only after all nodes are created. I changed the entry title and labels.

1 6

Issue 1043 in moose-technology: Can't load glamour on Pharo 2.0
by moose-technology＠googlecode.com 27 Jan '14

27 Jan '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1043 by damien.c...(a)gmail.com: Can't load glamour on Pharo 2.0 http://code.google.com/p/moose-technology/issues/detail?id=1043 $ wget --quiet -O - get.pharo.org/20+vm | bash $ ./pharo-ui Pharo.image config http://smalltalkhub.com/mc/Moose/Glamour/main ConfigurationOfGlamour --install=development --group="Core,Morphic,Roassal" This does not work anymore. MessageNotUnderstood: Character>>ensure: Character(Object)>>doesNotUnderstand: #ensure: MetacelloVersionConstructor(MetacelloAbstractVersionConstructor)>>with:during: MetacelloVersionConstructor>>specResolverBlock in Block: [:block | self with: versionSpec during: block] ByteString(SequenceableCollection)>>do: MetacelloVersionConstructor>>specResolverBlock in Block: [:attribute | | blockList | (blockList := self att...etc... OrderedCollection>>do: MetacelloVersionConstructor>>specResolverBlock in Block: [:versionSpec :pragma | (pragma argumentAt: 1)... MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: in Block: [:pragma | ... OrderedCollection>>do: MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: in Block: [:versionString :pragmaColl | ... Dictionary>>keysAndValuesDo: in Block: [:assoc | aBlock value: assoc key value: assoc val...etc... Dictionary>>associationsDo: in Block: [:each | each... Array(SequenceableCollection)>>do: Dictionary>>associationsDo: Dictionary>>keysAndValuesDo: MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: MetacelloVersionConstructor>>calculate:project: MetacelloVersionConstructor>>on: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: MetacelloVersionConstructor>>on: MetacelloVersionConstructor class>>on: ConfigurationOfGlamour>>project ConfigurationOfGlamour class>>project ConfigurationCommandLineHandler>>project ConfigurationCommandLineHandler>>metacelloVersion: -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

4 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev