- Moose-dev - INF Mailman

What is the relevence of referenceVersion in Hismo?

by badja

In the description of Girba, 2005, "Modeling History to understand Software Evolution", there is a small statement on "referenceVersion" in the Hismo metamodel: "Each Version has a reference to the so called referenceVersion which provides a fixed point in the historical space." This is implemented in Moose Hismo, but there is little description of its relevence to modelling. What is meant by "fixed point in the historical space"? In fact, there is an interface to set it to easily set it to nil!! (HismoEntityVersion class >> with:inHistory:) Can Tudor or someone else able to describe why referenceVersion would be important in time based analysis? Could this be, for example, the "baseline" to which other copies are compared? Can we have a different referenceVersions in different HismoHistoryGroups? Can we change the referenceVersion on the fly during analysis? I can see hints in the names of methods (e.g. isBornPriorToOrInReferenceVersion), but I can't quite catch the semantics. Can you give some guidelines on which version should be selected as the referenceVersion, and why? As I've described earlier, I'm trying to analyse different versions of system development schedules. I'm trying to use the Hismo framework to its best advantage, so I'm trying to understand the semantics as well as the code. Alan. -- View this message in context: http://forum.world.st/What-is-the-relevence-of-referenceVersion-in-Hismo-tp… Sent from the Moose mailing list archive at Nabble.com.

12 years

5
11
0 0

Issue 829 in moose-technology: Roassal Label Text does not scale with Zoom Out

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 829 by google....(a)ben.coman.com.au: Roassal Label Text does not scale with Zoom Out http://code.google.com/p/moose-technology/issues/detail?id=829 Actions 1. Open Roassal Easel > Example > #arrowed edges > umlLike 2. Click the <Zoom out> button multiple times Expected Behaviour Text gets smaller so as to stay within the border as the label box gets smaller. Observed Behaviour Only the border of the label gets smaller. The text gets the same size until it all overlaps.

12 years

1
4
0 0

Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)

by moose-technology＠googlecode.com

Updates: Summary: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736 (No comment was entered for this change.)

12 years

4
15
0 0

Issue 647 in moose-technology: Integrate torch package visualization

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 647 by cy.delau...(a)gmail.com: Integrate torch package visualization http://code.google.com/p/moose-technology/issues/detail?id=647 Maybe it would be a good idea (?) to use / integrate the torch packages visualization in moose ? http://hal.archives-ouvertes.fr/docs/00/53/15/08/PDF/Uqui10a-Torch-WCRE10.p…

12 years

2
4
0 0

Re: Issue 469 in moose-technology: integrate Kontractor

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.3 Comment #4 on issue 469 by tudor.girba: integrate Kontractor http://code.google.com/p/moose-technology/issues/detail?id=469 What is the status of this?

12 years

1
3
0 0

Re: Issue 437 in moose-technology: Text is not affected by zooming in Mondrian

by moose-technology＠googlecode.com

Comment #1 on issue 437 by alexandre.bergel: Text is not affected by zooming in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=437 Situation has been slightly improved, but this is clearly not satisfactory

12 years

1
4
0 0

Re: Issue 401 in moose-technology: fromPositions: and toPositions:

by moose-technology＠googlecode.com

Updates: Status: WontFix Comment #2 on issue 401 by tu...(a)tudorgirba.com: fromPositions: and toPositions: http://code.google.com/p/moose-technology/issues/detail?id=401 (No comment was entered for this change.) -- 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

12 years

1
0
0 0

Re: PetitJava performance

by Stephan Eggermont

Chris wrote: >Interestingly, Stephan has commented most of the other nodes - thanks! Can't claim that. We tried merging with the last version and had conflicts. We then used an earlier version that merged. Good to see it working though. I noticed you're committing as both cbc and ChrisCunningham? Seems to confuse smalltalkhub (it can't find user ChrisCunningham). Stephan

12 years

3
3
0 0

DNU: FAMIXStructuralEntity>>declaredType:

by Johan Fabry

Hi All, it has been a while for me, so apologies in advance if this is known/stupid/... I have not worked on at AspectMaps in a looooong time, and now I am assessing (heh) the effort of getting it up to date to the latest version of Moose. (Last working version is for 4.3) It has been going reasonably well, but now I have encountered something in the custom importer that has me stumped. Any pointers on how to resolve this would be most helpful. FAMIXStructuralEntity>>declaredType: throws a DNU because it ends up sending #structuresWithDeclaredType to the ByteString 'method' when executing FMMultiValueLink class>>on: update: from: to: The only guys that understand that messages are FAMIXType instances. This is weird to me because there is no obvious relation between 'method' and any FAMIXType instances. Can anybody point me to a solution? ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

12 years

2
4
0 0

Moose On The Web

by Vincent BLONDEAU

Hi, I want to share with you a screenshot of the first version of the web client for the Moose On Web Project. It's based on Amber and use a Rest Api to interact with the Moose image. A demo version will be online next week ! Cheers, Vincent

12 years

3
2
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/601/> ------------------------------------------ Started by upstream project "roassal" build number 285 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/hudson1002745009547870045.sh + wget --quiet -O - http://get.pharo.org/20+vm + bash 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: PetitSmalltalk [PetitSmalltalk] in cache ERROR: 'GoferRepositoryError: Could not access http://www.smalltalkhub.com/mc/Moose/PetitParser/main: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mMetacelloLoadingMCSpecLoader(Object)>>error: MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>resolvePackageSpec:gofer: MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirectives:gofer: in Block: [:packageLoadDirective | ... OrderedCollection>>do: MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirectives:gofer: in Block: [| goferLoad loadBlock answers |... 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: MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirectives:gofer: MetacelloAtomicLoadDirective>>finalizeLoad: MetacelloAtomicLoadDirective>>loadLinearLoadDirective:gofer: MetacelloLinearLoadDirective>>loadUsing:gofer: MetacelloAtomicLoadDirective>>loadAtomicLoadDirective:gofer: in Block: [:directive | directive loadUsing: self gofer: aGo...etc... OrderedCollection>>do: MetacelloAtomicLoadDirective>>loadAtomicLoadDirective:gofer: MetacelloAtomicLoadDirective>>loadUsing:gofer: MetacelloAtomicLoadDirective>>loadAtomicLoadDirective:gofer: in Block: [:directive | directive loadUsing: self gofer: aGo...etc... OrderedCollection>>do: MetacelloAtomicLoadDirective>>loadAtomicLoadDirective:gofer: MetacelloAtomicLoadDirective>>loadUsing:gofer: MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadAtomicLoadDirective:gofer: in Block: [:directive | directive loadUsing: aLoaderDirectiv...etc... OrderedCollection>>do: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: PetitSmalltalk [PetitSmalltalk] in cache ERROR: 'GoferRepositoryError: Could not access http://www.smalltalkhub.com/mc/Moose/PetitParser/main: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years

1
0
0 0

hygiene

by Tudor Girba

Hi, The Moose builds got messy: - there are extensions that do not load - there are tests that fail https://ci.inria.fr/moose/ Please let us stop for a moment and clean the mess. It's a question of hygiene. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years

3
3
0 0

what is EyeContextInspector?

by Tudor Girba

Hi, ConfigurationOfGToolkit wants to load some extensions to EyeContextInspector. But, where is this class coming from? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years

2
3
0 0

dependencies to glamour

by Tudor Girba

Hi, I noticed that both ConfigurationOfPetitParser and ConfigurationOfGToolkit are loading only the Core and Morphic groups from Glamour. However, the code inside depends on visualizations, too, and thus, it needs at least Roassal. So, now I added a Roassal group explicitly in the ConfigurationOfGlamour and had the two other configurations load the Roassal group as well. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years

1
0
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/596/> ------------------------------------------ Started by upstream project "petitparser" build number 108 originally caused by: [URLTrigger] A change within the response URL invocation (log) Started by upstream project "petitparser" build number 109 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/hudson6620740858054570258.sh + wget --quiet -O - http://get.pharo.org/20+vm + bash 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: Name not found: Rossal [0mMetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: in Block: [^ self error: 'Name not found: ' , aString] MetacelloMCVersionSpec>>packageNamed:forMap:ifAbsent: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: in Block: [:req | (self... Set>>do: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpecLoader>>resolveToLoadableSpecs 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: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... 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: MetacelloMCVersion>>fetchRequiredFromArray: MetacelloMCProjectSpec>>loadVersion: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] [0m[31mGot startup errors: [0m[31m Error: Name not found: Rossal [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years

1
0
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/593/> ------------------------------------------ [...truncated 1192 lines...] @ @ basicNew truncated class @ fractionPart truncated @ @ @ @ basicNew @ @ basicNew perform:with: perform:with: @ @ @ basicNew truncated @ @ @ @ fractionPart truncated fractionPart truncated @ @ @ species species basicAt: basicAt: bitShiftMagnitude: basicAt: bitOr: digitCompare: bitShiftMagnitude: perform:with: class perform:with: fractionPart truncated perform:with: @ @ basicNew @ @ basicNew perform:with: perform:with: @ @ @ basicNew truncated @ @ @ @ fractionPart truncated fractionPart truncated @ @ basicNew: replaceFrom:to:with:startingAt: at:put: class stringHash:initialHash: class class compare:with:collated: perform:with: @ perform:with: @ @ perform:with: @ basicNew @ @ @ perform:with: @ @ perform:with: @ basicNew @ shallowCopy shallowCopy shallowCopy @ @ new: at:put: at:put: at:put: at:put: species new: @ at:put: @ at:put: @ at:put: @ at:put: @ @ @ @ @ @ basicNew @ perform:with: @ @ perform:with: @ basicNew @ @ basicNew @ @ basicNew @ perform:with: @ @ perform:with: @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew @ @ @ @ basicNew compare:with:collated: new: at:put: at:put: perform:with: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: stack page bytes 4096 available headroom 3300 minimum unused headroom 3480 (last object overwritten) ./pharo: line 11: 10265 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@2f17e8fb:moose-ubuntu1204-dualproc-i386 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/Mondrian-Tests-Test.x…> 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 471 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Mondrian-Tests-Test.x…> : 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/Mondrian-Tests-Test.x…;> lineNumber: 471; 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

12 years

2
2
0 0

VM - Latest or Stable

by Usman Bhatti

Currently, we have a bug in the latest version of Pharo VM that does not allow a build to complete (Esteban is working to correct it) As the builds in Moose jenkins depend on the latest version of Pharo VM, we were unable to perform any build since 10 days (that also includes INRIA downtime). But the question is: Should Moose and other builds in the moose jenkins depend on the latest VM? Or we should depend on the stable version of the VM? Now, stable version is good but we dont have many bug fixes that are integrated in the latest version. For example, most of the builds in the jenkins are now unstable and I suspect that's being caused by the fact that we are now depending on the stable Pharo VM. I cannot verify it since the latest VM is buggy. Can you please see your respective builds and see why is jenkins becoming unstable? usman

12 years

3
2
0 0

Re: Graph-ET so far

by Alexandre Bergel

hi! I think your loading script should instead be: Gofer new smalltalkhubUser: 'DanielAvivNotario' project: 'Graph-ET'; package: 'Graph-ET'; load I was able to use Graph-ET in a Roassal easel. Cool! I think we should _always_ be able to do so. Here is a script: -=-=--=-=--=-=--=-=- view interaction popupView: [ :el :v | v shape rectangle. v node: 'node' forIt: [ | diag | diag := GETVerticalBarDiagram new. diag models: ((el methods collect: #numberOfLinesOfCode) asSortedCollection); height: 50; spacing: 2. diag generateIn: v raw. ] ]. view shape rectangle size: #numberOfMethods. view nodes: ROShape withAllSubclasses. view edgesFrom: #superclass. view treeLayout. -=-=--=-=--=-=--=-=- Aqui un screenshot de un popup view: Cheers, Alexandre On Jun 3, 2013, at 11:20 PM, Daniel Aviv Notario <daniel_avivnotario(a)hotmail.com> wrote: > Hi Doru! > > I send you this email to inform you of the stage of development in Graph-ET. > > I recently added all the interactions in EyeSee (pop-ups and hightlights) using Roassal's events and interactions. Because of the implementation in Graph-ET, I had to use a wrapper to make the syntax in EyeSee work, I tested them only in the bar chart so far. > > This week I'll work on adding the coloring to the bar charts. And maybe trying to understand and implement a little bit of the Axis and AxisStrategy hierarchy, as they represent most of the classes in EyeSee. Once coloring and axis are implemeted and tested on the bar charts, i'll port the other charts. > > Here's my Gofer to Graph-ET: > > Gofer new > smalltalkhubUser: ‘DanielAvivNotario’ > project: ‘Graph-ET’ > package: ‘Graph-ET’. > > Remember to upload first the last version of Roassal, as Alex made some changes that affect my code directly. > > > Hope you're doing great! Greetings, > > Daniel :-) -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years

2
1
0 0

Re: PetitJava performance

by Stephan Eggermont

Yuriy, Ok, I'm not in a hurry. Please note that your latest version is out of sync since PetitJava-MartinDias.104, and there are lots of versions to merge by cbc & ChrisCunningham. Automerge fails. Stephan

12 years

3
2
0 0

Roassal scalability

by Stéphane Ducasse

Hi I'm sorry may be I'm too dull but I did not understand the plan for the GSOC of Matthieu. Igor told us a while ago that athens offers transformation matrix that could really speed up Roassal. Now is there a plan to use that in Roassal? If Roassal should stay platform independent then there should be a solution at its architectural level to have one library for Athens and one for the rest. In addition I do not understand how Roassal can work fast on amber while using Athens without again using the athens infrastructure. So I would like to know. Stef

12 years

8
30
0 0

tests are failing

by Tudor Girba

I am still on holidays, but I could not help to notice that all sorts of tests are failing :). Please take a look: https://ci.inria.fr/moose/ Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years

1
0
0 0

Issue 907 in moose-technology: VerveineJ does not export source anchors for FAMIXAnnotationType and FAMIXAnnotationTypeAttribute

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix New issue 907 by tu...(a)tudorgirba.com: VerveineJ does not export source anchors for FAMIXAnnotationType and FAMIXAnnotationTypeAttribute http://code.google.com/p/moose-technology/issues/detail?id=907 When we have an explicit annotation in the code, we should also get the source anchor associated with it. For example, in the below case, SomeAnnotation.java should be associated with SomeAnnotation: SomeAnnotation.java @Documented @Target({ ElementType.FIELD }) @Retention(RetentionPolicy.CLASS) public @interface SomeAnnotation {...} The same applies for the contained FAMIXAnnotationTypeAttributes.

12 years

1
3
0 0

PetitJava performance

by Stephan Eggermont

While working on PetitDelphi, we noticed significant performance problems. As PetitDelphi copied the design of PetitJava, we found the same root cause. When creating a new java parser, a significant amount of time is spend on initialization, especially the creation of parsers for keywords, separators and operators. The introduction of a lexicon cache allows the tests to run significantly faster. 2230 ms to 224ms the second time. PetitJava-DiegoLont.115 Yuriy, can you merge? Stephan

12 years

3
2
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/588/> ------------------------------------------ Started by upstream project "petitjava" build number 89 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/hudson7862730162219260867.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: MetacelloProjectSpecLoadError: No version found for '#stable' of ConfigurationOfNewDebugger [0mMetacelloMCProjectSpec>>loadVersion: MetacelloMCProjectSpec>>load MetacelloProjectReferenceSpec>>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: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... 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: [0m[31mGot startup errors: [0m[31m MetacelloProjectSpecLoadError: No version found for '#stable' of ConfigurationOfNewDebugger [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years

1
0
0 0

News from your work

by Guillaume Larcheveque

Hello Jan, We are really interested about your project on Island Grammar. I know that Stephane has some money to invite you to present your work and exchange about that. We would really like to hear and learn from you. Thanks in advance -- *Guillaume Larcheveque*

12 years

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev