Moose-dev January 2014

moose-dev@list.inf.unibe.ch

41 participants
119 discussions

by Vincent Blondeau

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

10 years, 2 months

Build failed in Jenkins: moose-5.0 #592

by admin＠moosetechnology.org

10 years, 2 months

roassal2 job sets the author

by Tudor Girba

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"

10 years, 2 months

Re: Build failed in Jenkins: roassal2 #50

by Alexandre Bergel

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

10 years, 2 months

Re: Issue 113 in moose-technology: Roassal should support lazy edges when used through the Mondrian API

by moose-technology＠googlecode.com

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.

10 years, 2 months

Issue 1043 in moose-technology: Can't load glamour on Pharo 2.0

by moose-technology＠googlecode.com

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

10 years, 2 months

Source city

by Diego Lont

Hi all, I wanted to try out source city in Moose 5.0. The current pharo version there is Pharo3.0 (Latest update: #30714), so note before loading you need to install the slice that belongs to issue 12488. So somewhere regressions occurred. But after installing this slice, you still have to fix the configuration. I attached a fixed configuration, as I am not allowed to put it in the right spot. If someone could upload this, I would be much obliged. Cheers, Diego

10 years, 2 months

Re: Issue 1043 in moose-technology: Can't load glamour on Pharo 2.0

by Stephan Eggermont

I guess you need something similar to this in ConfigurationOfGlamour>stable spec for: #'common' version: '2.1'. spec for: #'pharo1.3.x' version: '2.2'. spec for: #'pharo1.4.x' version: '2.4'. spec for: #'pharo2.x' version: '2.5'. spec for: #'pharo3.x' version: '2.6-snapshot'.

10 years, 2 months

managing gtinspector extensions

by Tudor Girba

Hi, As you probably know by now, you can get the most our of the GTInspector by extending it with custom presentations. However, the problem that raises is how to manage these extensions? To solve this problem, just inspect the GTInspector and you will get a list with all these extensions. This list also serves as a set of examples that you can learn from. And because most of these extensions require just one method, you get a rather effective browser. [image: Inline image 1] You can see a more detailed explanation here: http://www.humane-assessment.com/blog/managing-gtinspector-extensions What else would you need in the GTInspector? Let me know what you think. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 2 months

www.moosetechnology.org down?

by NISHIHARA Satoshi

is http://www.moosetechnology.org/ down? best regards. -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

10 years, 2 months

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev January 2014