Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

better rubric-glamour integration
by Tudor Girba 05 Aug '13

05 Aug '13

Hi, Alain took some time and provided an enhanced integration of Rubric into Glamour. This means that now you can use all the power of Rubric from Glamour. For example, select a class from a system parsed with VerveineJ, then open it in a Glamour Editor, and then use this code: composer rubricText with: [ :r | r display: [ :c | class sourceAnchor completeText ]. class methods do: [ :m | | seg | m sourceAnchor notNil ifTrue: [ seg := RubTextSegmentMorph from: m sourceAnchor interval first to: m sourceAnchor interval last + 1. seg color: Color paleYellow. seg icon: MooseIcons famixMethod. seg label: 'Explore'. seg iconBlock: [ :segment :event | m explore ]. r addTextSegment: seg ] ] ]. composer startOn: class You get all methods in the class highlighted and you can interact with them (see the attached screenshot). This is highly promising. For more examples, look at GLMRubricExample and its subclasses. The next step will be to replace altogether the default text presentation with the new Rubric rendering. Cheers, Doru [image: Inline image 1] -- www.tudorgirba.com "Every thing has its own flow"

2 1

Jenkins build became unstable: moose-latest-dev-4.8 #791
by admin＠moosetechnology.org 04 Aug '13

04 Aug '13

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

1 1

Jenkins build became unstable: moose-latest-dev-4.8 #786
by admin＠moosetechnology.org 02 Aug '13

02 Aug '13

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

1 1

FamixDiff
by Nicolas Anquetil 01 Aug '13

01 Aug '13

announcing version 0.9 of FamixDiff: MCHttpRepository location: 'http://www.smalltalkhub.com/mc/Moose/FamixDiff/main' user: '' password: '' With Anne, we have been working on a diffing algorithm between Famix models. The idea is that having models of two versions of the same system, you can generate the list of changes (add/delete/move/rename) that bring the first model to the second. Still work in progress, but we are dealing with the main entities: package/namespaces, classes, methods, variables Nicolas (& Anne) -- Nicolas Anquetil -- RMod research team (Inria)

2 4

Random graph generators
by Serge Stinckwich 31 Jul '13

31 Jul '13

Dear all, I'm currently working on random graph generators based on Moose-Algos-Graph library. The G(n,m) and G(n,p) Erdos Renyi model are already implemented. Barabási–Albert models will be implemented soon. The repository is here if you want to contribute: http://smalltalkhub.com/#!/~SergeStinckwich/Moose-Algos-Graph-Generators/ Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1

FAMIX Project
by Usman Bhatti 31 Jul '13

31 Jul '13

Hello. There is a FAMIX project in Moose team that was created by me and Nicolas intended to contain FAMIX code when we started to move Moose to Smalltalkhub. Finally we didn't use FAMIX project in Moose team to contain FAMIX meta-model code but we moved it to Moose project because Moose and FAMIX are intended to be used together. Question: Can we delete FAMIX project in Moose team as it hasn't moved since feb 2013? best. Usman and Nicolas

2 1

[ann] a snappier snapshotcello
by Tudor Girba 30 Jul '13

30 Jul '13

Hi, A new version of Snapshotcello is now reachable from your Pharo 2.0 image. Besides snapshotting the current version, you now get the possibility of: - marking the new version as stable, - committing the configuration package, and - pushing the package to the official Pharo repository. Here is an example: Snapshotcello new configurationClass: ConfigurationOfSnapshotcello; sourceVersion: #development; targetVersion: '1.4-snapshot'; snapshot; makeStableFor: #'pharo2.x'; commit; pushToPharo20Repository A more detailed description can be found here: http://www.tudorgirba.com/blog/snappier-snapshotcello We can certainly improve this, and it would be great to have a similar mechanism integrated into Metacello. But, in the meantime, I find myself for the first time literally one do-it away from distributing projects that are developed without much constraints. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

2 1

preparing the 4.8 release
by Tudor Girba 30 Jul '13

30 Jul '13

Hi, I finished the last couple of issues for 4.8, and now I am preparing the release. In the process, I will release also: - MooseAlgos - Fame - Mondrian - EyeSee - Roassal (just for reference) - Glamour - PetitParser - Glamorous Toolkit The snapshots will be marked as stable and will be published in: http://ss3.gemtalksystems.com/ss/MetaRepoForPharo20/ Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 1

Build failed in Jenkins: moose-latest-dev-4.8 #772
by admin＠moosetechnology.org 30 Jul '13

30 Jul '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/772/> ------------------------------------------ [...truncated 680 lines...] tempAt: class tempAt: tempAt:put: tempAt: tempAt:put: findNextUnwindContextUpTo: terminateTo: basicNew at: basicNew findNextHandlerContextStarting tempAt: class tempAt: tempAt:put: tempAt: class class class class class class class class class class class class class class tempAt:put: findNextUnwindContextUpTo: terminateTo: at: basicNew findNextHandlerContextStarting tempAt: class tempAt: tempAt:put: tempAt: class class class class class class class class class class class class class class tempAt:put: findNextUnwindContextUpTo: terminateTo: class new: at:put: at:put: at:put: instVarAt: basicNew new: new: at:put: at:put: new: at:put: at:put: at:put: at:put: at:put: instVarAt: at:put: at:put: instVarAt: at:put: at:put: at:put: at:put: class new: at:put: at:put: at:put: instVarAt: basicNew new: new: at:put: at:put: new: at:put: at:put: at:put: at:put: at:put: instVarAt: at:put: at:put: instVarAt: at:put: at:put: instVarAt: at:put: at:put: instVarAt: at:put: at:put: instVarAt: at:put: at:put: basicSize class class fuelPointsTo: class at:put: objectAt: objectAt: objectAt: objectAt: objectAt: objectAt: objectAt: at:put: at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: class at:put: at:put: class class basicNew basicNew new: at:put: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: new: stack page bytes 4096 available headroom 3300 minimum unused headroom 3500 (last object overwritten) ./pharo: line 11: 22517 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" -nodisplay "$@" Build 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@3117341c:moose-slave at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:825) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) 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:244) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:140) at hudson.tasks.junit.TestResult.<init>(TestResult.java:116) 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:2309) 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 49 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:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:227) ... 15 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: 49; 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) ... 18 more

1 1

Mixing layout
by mathieubmddehouck＠mailoo.org 29 Jul '13

29 Jul '13

Hi Working on a mixing layout. Something really nice. But still have a problem. What do we do when there are several elements with the same model ? First, it causes troubles with look up, and so with edges... And then for layout also. Regards Mathieu

3 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev