Moose-dev July 2013

moose-dev@list.inf.unibe.ch

28 participants
130 discussions

Re: Build failed in Jenkins: moose-latest-dev-4.8 #658

by Stephan Eggermont

Hmm, not able to access squeaksource. Are there dependencies that should move to smalltalkhub or ss3 (like OSProcess)? July 15th Squeaksource will become static. Stephan

11 years, 11 months

Re: [Pharo-dev] Sunburst visualization

by Tudor Girba

This looks like really a fantastic job. I cannot wait to see the code :) Doru On Jul 4, 2013, at 3:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > We are currently working on a Sunburst based on top of Roassal. Milton is doing a fantastic job! > Here some early screenshots: > > <image copy 2.png><image copy.png><image.png> > > > Milton & Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > -- www.tudorgirba.com "If you can't say why something is relevant, it probably isn't."

11 years, 11 months

Build failed in Jenkins: moose-latest-dev-4.8 #658

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/658/> ------------------------------------------ Started by upstream project "roassal" build number 304 originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson9025467938898833976.sh + + bash wget --quiet -O - http://get.pharo.org/20+vm Downloading the latest 20 Image: http://files.pharo.org/image/20/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 Please install the 32bit libraries sudo aptitude install ia32-libs + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: Error: Could not resolve: OSProcess [OSProcess] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.smalltalkhub.com/mc/Moose/Moose/main ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/OSProcess: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mMetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushAtomicLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: OSProcess [OSProcess] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.smalltalkhub.com/mc/Moose/Moose/main ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/OSProcess: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 11 months

Sunburst visualization

by Alexandre Bergel

Hi! We are currently working on a Sunburst based on top of Roassal. Milton is doing a fantastic job! Here some early screenshots: https://www.facebook.com/photo.php?fbid=478025185617417&set=a.3411893793009… https://www.facebook.com/photo.php?fbid=478024745617461&set=a.3411893793009… Cheers, Milton & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 11 months

Re: [Pharo-dev] Sunburst visualization

by Stéphane Ducasse

:) I'm happy With Athens a new space is opening :) Now do you handle interaction? Stef On Jul 4, 2013, at 3:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > We are currently working on a Sunburst based on top of Roassal. Milton is doing a fantastic job! > Here some early screenshots: > > <image copy 2.png><image copy.png><image.png> > > > Milton & Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

11 years, 11 months

Roassal 3d is on its way

by Alexandre Bergel

One good news never come alone :-) We are working on a 3d version of Roassal. Here is a preliminary screenshot: More to come soon! Cheers, Ronie, Milton, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 11 months

Roassal Scalability

by mathieubmddehouck＠mailoo.org

Hi I have Roassal as speed with 30,000 elements as with 1,000 elements. But still I have to udpate the view when resizing the window and translating the view. Does anyone know how to send the view an event when I resize the view ? Regards Mathieu

11 years, 11 months

Implementation of isPackage, isClass...

by Anne Etien

Hi, The isPackage method is implemented only in FAMIXNamedEntity (and obviously in FAMIXPackage). The isClass method is implemented only in FAMIXSourcedEntity (and obviously in FAMIXClass). The isAttribute method is implemented only in FAMIXStructuralEntity (and obviously in FAMIXAttribute). The isMethod method is not implemented… Why not harmonizing this and defining all these methods in FAMIXEntity? In fact, I am working with Nicolas Anquetil on the diff of models. I would like to create an Orion action for each change. Thus, if a class is added between version n and version n+1, I would like to instantiate an AddClass operator. And so on for each change. So I need to know the type of the FAMIXEntity on which the change occurred. Using these methods would be tidier than using isKindOf: method. Please let me know if such implementations make sense for you or not. Anne

11 years, 11 months

Petit Java

by Diego Lont

Hi all, I try to make sense of Petit Java and the discussions around it, because it makes sense to have a similar architecture for Petit Delphi. The Delphi syntax contains 141 rules, versus 137 rules in java. So we compare pretty closely. But when I try to read the petit java code, I notice some odd things, so maybe someone can tell me why things are as they are. I thought AST meant we have an Abstract Syntax Tree. A syntax tree, that only contains the information needed. The way we do it on the Delphi side, is that only when we have a purpose for a certain AST Node we create it. On the detail level, we do not have many AST nodes yet, since we only generate FAMIX to the method level. And the number of AST nodes is growing fast. Why does the AST needs to stick to the java grammar as closely as possible? When I look at the AST Node and at the places where they are created, they more look like grammar nodes than syntax nodes. I have a node called MethodDeclarationNode. But it is created in the rule "methodNotConstructorDeclaration" and when I look at the rule "methodDeclaration" I would expect to have 2 subclasses: a ConstructorDeclarationNode and a MethodNotConstructorDeclarationNode … but instead I have a subclass InterfaceMethodDeclarationNode. I thought FAMIX was meant for this and that is why we convert our AST into FAMIX as well … In PetitJava there is a visitor for the AST. I do not see how this visitor helps. The AST is changing faster than the implementors of the visitor, not only because we are evolving Petit Java, but also because Java itself also evolves and will make changes to the language in the future. I see only a few possible implementors of this visitor. And maybe some of the Petit Java developers want to take a look at the Petit Delphi code. Because I am sure we did things good and also some stupid things, so please help us find the stupid things and copy the good things! I know I try to copy the good ideas from petit java. Regards, Diego

11 years, 11 months

fast job is broken

by Tudor Girba

Hi, The FAST job is broken since a week: https://ci.inria.fr/moose/job/FAST-On-Moose/ Please take a look at the problems. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 11 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2013