Moose-dev September 2013

moose-dev@list.inf.unibe.ch

30 participants
148 discussions

Start a nNew thread

Jenkins build became unstable: moose-latest-dev-4.8 #1106
by admin＠moosetechnology.org 14 Sep '13

14 Sep '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1106/>

3 3

Hierarchical Bundle Edges
by Alexandre Bergel 14 Sep '13

14 Sep '13

Hi! The BSpline package allows one to define hierarchical bundle edges. These screenshots have been made using the script below, runnable in a Glamour-based Roassal Easel open on a class group in Moose. More screenshot on : https://www.facebook.com/media/set/?set=a.511442275609041.1073741827.340543… Cheers, Alexandre |bs superclassEdges lastlevel| view shape circle size: 10. view nodes: classGroup. superclassEdges := view edgesFrom: #superclass. " view treeLayout userDefinedEdges: superclassEdges. " view radialTreeLayout userDefinedEdges: superclassEdges. " view forceBasedLayout userDefinedEdges: superclassEdges. " lastlevel := classGroup select: [ :cls | (cls subclassHierarchy size) == 0 ]. "Blue" bs := (ROBSplineLine new). bs alpha: 0.8. bs setDiscovery: [ :cls | cls superclass ]. bs color: (Color blue alpha: 0.3). view shape: bs. view edges: lastlevel from: #yourself toAll: [ :cls | (cls queryAllOutgoingInvocations atTypeScope) select: [:clsa | (clsa subclassHierarchy size) == 0 and: [ cls name size odd ] ]]. "Red" bs := (ROBSplineLine new). bs alpha: 0.8. bs setDiscovery: [ :cls | cls superclass ]. bs color: (Color red alpha: 0.3). view shape: bs. view edges: lastlevel from: #yourself toAll: [ :cls | (cls queryAllOutgoingInvocations atTypeScope) select: [:clsa | (clsa subclassHierarchy size) == 0 and: [ cls name size even ] ]]. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 3

short bug fixing period
by Tudor Girba 14 Sep '13

14 Sep '13

Hi, I would like to allow a short period of about 1-2 weeks for bug fixing before we move to Pharo 3.0. So, in case you notice a problem, please report it as soon as possible. Once we move to Pharo 3.0, we will no longer support Pharo 2.0 for bug fixes. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

3 4

Build failed in Jenkins: moose-latest-dev-4.8 #1104
by admin＠moosetechnology.org 14 Sep '13

14 Sep '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1104/> ------------------------------------------ Started by upstream project "roassal" build number 473 originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-slave 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/hudson9175072361312431320.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest 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/latest.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 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+ ./pharo moose-latest-dev-4.8.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1104/ + ./pharo moose-latest-dev-4.8.image moosetest --junit-xml-output [31m[33m =============================================================================== Notice: Running tests in 138 Packages =============================================================================== [0m[0m[31mError: index out of range [0mTabSelectorMorph(Object)>>error: TabSelectorMorph(Morph)>>privateAddAllMorphs:atIndex: TabSelectorMorph(Morph)>>addAllMorphs: TabSelectorMorph>>updateTabs TabSelectorMorph>>extent: TabSelectorMorph(Morph)>>bounds: TabSelectorMorph(Morph)>>layoutInBounds: TableLayout>>layoutLeftToRight:in: TableLayout>>layout:in: PanelMorph(Morph)>>doLayoutIn: PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: PanelMorph(Morph)>>fullBounds LazyTabGroupMorph(Morph)>>submorphBounds in Block: [:m | | subBox | m visible... Array(SequenceableCollection)>>do: LazyTabGroupMorph(Morph)>>submorphBounds LazyTabGroupMorph(Morph)>>privateFullBounds LazyTabGroupMorph(Morph)>>doLayoutIn: LazyTabGroupMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: LazyTabGroupMorph(Morph)>>fullBounds LazyTabGroupMorph(Morph)>>layoutProportionallyIn: ProportionalLayout>>layout:in: in Block: [:m | m layoutProportionallyIn: newBounds] Array(SequenceableCollection)>>do: PanelMorph(Morph)>>submorphsDo: ProportionalLayout>>layout:in: PanelMorph(Morph)>>doLayoutIn: PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: PanelMorph(Morph)>>fullBounds [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results ERROR: Failed to archive test reports hudson.util.IOException2: remote file operation failed: <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> at hudson.remoting.Channel@69c39cb2:moose-slave at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:882) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:121) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1628) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Caused by: hudson.util.IOException2: Failed to read <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic…> at hudson.tasks.junit.TestResult.parse(TestResult.java:291) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:230) at hudson.tasks.junit.TestResult.parse(TestResult.java:165) at hudson.tasks.junit.TestResult.parse(TestResult.java:148) at hudson.tasks.junit.TestResult.<init>(TestResult.java:124) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2417) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: org.dom4j.DocumentException: Error on line 53 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic…> : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:130) at hudson.tasks.junit.TestResult.parse(TestResult.java:274) ... 16 more Caused by: org.xml.sax.SAXParseException; systemId: file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic…;> lineNumber: 53; columnNumber: 1; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:391) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1404) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:882) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:582) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1370) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1740) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1393) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2769) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) at org.dom4j.io.SAXReader.read(SAXReader.java:465) ... 19 more

1 1

Roassal
by Alexandre Bergel 14 Sep '13

14 Sep '13

Hi! Some news for Roassal: - RoassalExtras is a new package that will contains some cool contributions. The configuration is updated. So far, only BSpline is in it. Screenshots are below. - ConfigurationOfRoassal will be update only for major release. The versionning is moved to a new project I have worked on called VersionOfRoassal. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[ann] moose 4.8
by Tudor Girba 13 Sep '13

13 Sep '13

We are happy to announce version 4.8 of the Moose Suite: http://moosetechnology.org/download/4.8 Description -- This was supposed to be a minor release, but in the end it turned out to be a major release with significant improvements. The key highlights are: - Based on Pharo 2.0. - All built-in visualizations use Roassal. - Roassal received a significant performance boost and new smart graph layouts like TreeMapLayout or ForceBasedLayout. - Roassal uses Athens for nice looking vectorial graphics. - New charting engine based on Roassal: Graph-ET. - Glamour changed to enable dynamic scripts, while still remaining backward compatible. - Glamour received a RubricTextPresentation for using the new Rubric text morph. - Glamour, Roassal, EyeSee, Graph-ET editors are more robust when dealing with errors in scripts.- New GTDebugger with dedicated workflows for Announcements, PetitParser and Glamour itself. - Extended GTInspector for several object types. - Usable version of GTMetaceller for handling Metacello configurations. - FAMIX was strengthen to handle functions better in various programming languages. - New free type fonts and simpler whitespace-loving theme. - Lower memory footprint for large models. - Faster MSE import. A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Installation -- The Moose Suite 4.8 comes for each platform as a separate bundle: - Mac: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip - Windows: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip - Linux: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zip The Moose Suite 4.8 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. ((Smalltalk at: #ConfigurationOfMoose) project version: '4.8-snapshot') load Enjoy, The Moose Team -- www.tudorgirba.com "Every thing has its own flow"

4 4

Issue 950 in moose-technology: Freeze 4.8
by moose-technology＠googlecode.com 13 Sep '13

13 Sep '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Maintainability Milestone-4.8 New issue 950 by tu...(a)tudorgirba.com: Freeze 4.8 http://code.google.com/p/moose-technology/issues/detail?id=950 We need to freeze 4.8 for ConfigurationOfMoose and the configurations of all other Moose projects. We should extend the mechanism used for 4.7. -- 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

1 2

A Layered Grammar of Graphics
by Serge Stinckwich 12 Sep '13

12 Sep '13

Hi Moosers, this paper might be interesting to some of you: @Article{layered-grammar, author = {Hadley Wickham}, doi = {10.1198/jcgs.2009.07098}, journal = {Journal of Computational and Graphical Statistics}, number = {1}, pages = {3–28}, selected = {TRUE}, title = {A layered grammar of graphics}, volume = {19}, year = {2010}, } http://vita.had.co.nz/papers/layered-grammar.html I was wondering if Graph-ET (or EyeSee before) is close to this compositional approach ? Apparently at the moment, there is no interaction in this work (compare to Graph-ET). Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

3 4

How to get the MooseModel of a FAMIXType
by Johan Fabry 11 Sep '13

11 Sep '13

Hi all, I am a bit lost I'm afraid: I would like to know what the moose model is that contains a FAMIXType that I have been given. But I do not see how I can navigate from this type to the MooseModel that contains it. Can anybody give me the magic line of code for that? Thanks in advance! ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

3 3

graphet integrated in glamour
by Tudor Girba 10 Sep '13

10 Sep '13

Hi, GraphET is properly integrated in Glamour. You can play with it via: - open the GraphET editor from the Moose world menu - paste something like: chart lineDiagram models: (1 to: 10) Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

5 8

← Newer
1
...
8
9
10
11
12
13
14
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2013