- Moose-dev - INF Mailman

Issue 748 in moose-technology: DistributionMap examples not working

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 748 by cy.delau...(a)gmail.com: DistributionMap examples not working http://code.google.com/p/moose-technology/issues/detail?id=748 When you try to execute the examples in the class side of DistributionMap, you get an error. This bug looks complicate and it does not seem to be related to distributionMap: When I debug and I go down to the method DistributionMap>>elementsWithProperty:inPart: If I insert this lign: (elementsAndPropertyValue keys detect: [:each | each == element]). it returns me one element. Then if I execute: (elementsAndPropertyValue at: element) I have a KeyNotFound error

12 years

1
3
0 0

Issue 555 in moose-technology: DSM improve visualization

by moose-technology＠googlecode.com

Status: New Owner: jannik.l...(a)gmail.com Labels: Type-Defect Priority-Medium Component-DSM Milestone-4.4 New issue 555 by jannik.l...(a)gmail.com: DSM improve visualization http://code.google.com/p/moose-technology/issues/detail?id=555 I made the structure for DSM visualization. Now, I should create script for each and make communications between them coherent.

12 years

1
2
0 0

Re: Issue 482 in moose-technology: Use JNIPort to connect to VerveineJ

by moose-technology＠googlecode.com

Comment #2 on issue 482 by cy.delaunay: Use JNIPort to connect to VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=482 you should now use that: Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPort-Initialization'; load. Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPortExample'; load. The initialization part still has to be fixed, sometimes it works, sometimes not.

12 years

2
4
0 0

Re: Issue 432 in moose-technology: Popup should appear only when a certain modifier key is pressed

by moose-technology＠googlecode.com

Comment #1 on issue 432 by tu...(a)tudorgirba.com: Popup should appear only when a certain modifier key is pressed http://code.google.com/p/moose-technology/issues/detail?id=432 Another option would be to have the rendering happening in another thread.

12 years

1
8
0 0

Re: Issue 162 in moose-technology: Refactor FAMIX extensions

by moose-technology＠googlecode.com

Comment #4 on issue 162 by tu...(a)tudorgirba.com: Refactor FAMIX extensions http://code.google.com/p/moose-technology/issues/detail?id=162 This issue was already addressed -- 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
1
0 0

Re: Issue 43 in moose-technology: [FAME] add helper methods for multivalued attributes

by moose-technology＠googlecode.com

Updates: Status: WontFix Comment #4 on issue 43 by tu...(a)tudorgirba.com: [FAME] add helper methods for multivalued attributes http://code.google.com/p/moose-technology/issues/detail?id=43 This issue is too old and it is unlikely it will get addressed. -- 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

Issue 912 in moose-technology: Glamour presentations should update their own actions when receiving GLMPresentationUpdated

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 912 by chisvasi...(a)gmail.com: Glamour presentations should update their own actions when receiving GLMPresentationUpdated http://code.google.com/p/moose-technology/issues/detail?id=912 Right now when a presentation receives GLMPresentationUpdated it does not update its own actions. For example bellow is some code to see this behaviour. When the action from the composite presentation is triggered it updates the action from the contained presentations but not its action. Also if there is just one presentation in the composite then, due to how a composite with one presentation is implemented, it won't update any action. |browser| browser := GLMTabulator new. browser row: #aRow. browser transmit to: #aRow; andShow: [ :composite | composite title: 'Composite'; updateOn: Announcement from: [ browser announcer ]; dynamicActions: [ :list || actions | actions := OrderedCollection new. actions add: ((GLMGenericAction new) action: [ :presentation :model | browser announce: Announcement]; icon: GLMUIThemeExtraIcons glamorousAdd; title: DateAndTime now asString; yourself). actions ]. composite list title: 'List 1'; updateOn: Announcement from: [ browser announcer ]; dynamicActions: [ :list || actions | actions := OrderedCollection new. actions add: ((GLMGenericAction new) action: [ :presentation :model | browser announce: Announcement]; icon: GLMUIThemeExtraIcons glamorousAdd; title: DateAndTime now asString; yourself). actions ]. composite list title: 'List 2']. browser openOn: (1 to: 10)

12 years

1
4
0 0

Issue 926 in moose-technology: Moose should offer ZeroConf support for quick installations

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Milestone-4.8 Maintainability New issue 926 by tu...(a)tudorgirba.com: Moose should offer ZeroConf support for quick installations http://code.google.com/p/moose-technology/issues/detail?id=926 Moose should offer the same support for quick installations as Pharo does. -- 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
8
0 0

Issue 948 in moose-technology: mooseNameOn: uses signatureFromSmalltalkSelector

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 948 by step...(a)stack.nl: mooseNameOn: uses signatureFromSmalltalkSelector http://code.google.com/p/moose-technology/issues/detail?id=948 FAMIXMethod mooseNameOn: aStream has an interesting implementation. Is there a special reason not to use the signature when it is defined, instead of the signatureFromSmalltalkSelector? Doru wrote: This is horrible! Indeed, we should use the signature there, and the signatureFromSmalltalkSelector should disappear (because it should be set at import time). 4.8 Development -- 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
1
0 0

Issue 949 in moose-technology: FAMIXMethod isConstructor: aBoolean ignores the parameter

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 949 by step...(a)stack.nl: FAMIXMethod isConstructor: aBoolean ignores the parameter http://code.google.com/p/moose-technology/issues/detail?id=949 isConstructor: aBoolean self kind: #constructor Please fill in the labels with the following information: * Type-Defect, * Component-Famix -- 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
4
0 0

PetitJava madness

by Yuriy Tymchuk

What negation is doing in MethodInvocation node? And what negation is doing in the VariableAccessorNode? What type cast is doing in VariableAccessorNode? Why does variable accessor has array? Is't not accessor_s_. Accessor. Only one. Accessor only knows only name of the variable it's accessing and the target of access. During parsing PJVariableAccessorNode is created as part of identifierWithAccessors, primary and selector grammars. As for me this is madness. Yes, I made some mess to when I created InfixOperation instead of all the additive expressions, multiplicative expressions, etc... But to do it right now you just have to define a new node and create it for a related grammar instead of infix expression node. I think that right now PetitJava is a bigger mess than it was Надіслано з iPhone

12 years

2
4
0 0

Improving Roassal Scalability

by mathieubmddehouck＠mailoo.org

Hi I just begin looking after point of optimisation into Roassal and I there are different points : - firstly, it is not easy to profile - it seems that when we move the mouse on the visualisation then it draws everything each time we move the mouse. And of course the biggest the visualisation is, the hottest the computer is to be. So maybe we should either, only draw the visible things (we must know what is visible easily), or we should draw the whole visualisation as a picture (bitmap or svg ) in a buffer and then just navigate in it, and keeping a list of visible things (not to be drawn but to be checked for interactions). I think the picture is a good solution (maybe not a perfect one) since refreshing a picture is fine easier than redrawing the whole visualisation. And we should only draw changing elements with another color when dragging them. What do you think about that ?? Regards Mathieu

12 years

5
4
0 0

PetitDelphi status update

by Stephan Eggermont

Hi Doru, hope you had nice holidays :) We are making some nice progress. In about 5 minutes, parsing 8 MB of Delphi source in 87 units. So still some room for improvement. We can now show a dfm form outline. PDDelphiPanel open Select a .dpr file Select the model Select a unit with a form Diego & Stephan

12 years

3
2
0 0

Re: Moosename

by Stephan Eggermont

http://code.google.com/p/moose-technology/issues/detail?id=948

12 years

1
0
0 0

Moosename

by Stephan Eggermont

FAMIXMethod mooseNameOn: aStream has an interesting implementation. Is there a special reason not to use the signature when it is defined, instead of the signatureFromSmalltalkSelector? Diego & Stephan

12 years

2
1
0 0

Re: Performance profiling of PetitDelphi

by Stephan Eggermont

Thanks Doru. Hmm, you might want to avoid pasting a 1MB text into the sample area of PetitParser browser. 100% cpu and uninterruptable for quite some time now. Stephan

12 years

1
0
0 0

Performance profiling of PetitDelphi

by Stephan Eggermont

5 minutes for parsing 8MB is not very good, especially for people used to Delphi compilation speed. Any hints on how to profile the PDDelphiParser? I'm sure there are lots of very inefficient productions. Just counting method sends? Cheers, Stephan

12 years

2
1
0 0

Issue 931 in moose-technology: Moose Meta Browser - type and opposite values clipped on left

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 931 by alan.mcn...(a)gmail.com: Moose Meta Browser - type and opposite values clipped on left http://code.google.com/p/moose-technology/issues/detail?id=931 On selecing an Entity in the top left panel of the Moose Meta Browser, the Relation name/type/opposite are displayed. While the name is well displayed, the display of the type and opposite values are clipped on the left, and part of the first character cannot be seen. Similarly, if Property tab is selected, the type values are similarly clipped. -- 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
4
0 0

Issue 934 in moose-technology: Moose Meta Browser - Entities panel not updated when selecting Entity in Map

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 934 by alan.mcn...(a)gmail.com: Moose Meta Browser - Entities panel not updated when selecting Entity in Map http://code.google.com/p/moose-technology/issues/detail?id=934 In the Map panel it is possible to select a box representing an Entity. When this is done, the Entity and its relationships are highlighted in red in the Map pane. Also, the Relations / Properties and Comments panes are updated with information for that Entity shown. However, the Entity pane is NOT updated. I would expect that the Entities pane would be changed so that the Entity selected in the Map pane would also be selected in the Entities pane, including expanding any Entity hierarchy as required. -- 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
3
0 0

Re: PetitDelphi status update

by Stephan Eggermont

Hmm, forum.world.st seems to have lost a mail. http://moose-dev.97923.n3.nabble.com/PetitDelphi-status-update-td4027969.ht… Stephan

12 years

1
0
0 0

Issue 947 in moose-technology: TextPresentations should support setting the selectionInterval on creation

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 947 by chisvasi...(a)gmail.com: TextPresentations should support setting the selectionInterval on creation http://code.google.com/p/moose-technology/issues/detail?id=947 When creating a text presentation the user should be able to specify a selectionInterval: GLMTextPresentation new selectionIntervalBlock: [ ... ] -- 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
10
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/610/> ------------------------------------------ Started by upstream project "petitjava" build number 96 originally caused by: Started by timer Started by upstream project "petitparser" build number 112 originally caused by: Started by timer Started by upstream project "roassal" build number 290 originally caused by: Started by timer 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/hudson1442340997866419567.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+ ./pharo moose-latest-dev-4.8.image mooseimagesetup + ./pharo moose-latest-dev-4.8.image moosetest --junit-xml-output [31m[33m =============================================================================== Notice: Running tests in 137 Packages =============================================================================== [0m[0m[31mMessageNotUnderstood: receiver of "hasPositiveExtent" is nil [0mUndefinedObject(Object)>>doesNotUnderstand: #hasPositiveExtent ScrollBar(Morph)>>invalidRect:from: ScrollBar(Morph)>>invalidRect: ScrollBar(Morph)>>position: ScrollBar(Morph)>>bounds: PaginatedMorphTreeMorph(ScrollPane)>>hResizeScrollBar PaginatedMorphTreeMorph>>hResizeScrollBar PaginatedMorphTreeMorph(ScrollPane)>>resizeScrollBars PaginatedMorphTreeMorph(ScrollPane)>>hideOrShowScrollBars PaginatedMorphTreeMorph(ScrollPane)>>extent: PaginatedMorphTreeMorph(MorphTreeMorph)>>extent: PaginatedMorphTreeMorph>>extent: PaginatedMorphTreeMorph(Morph)>>bounds: PaginatedMorphTreeMorph(Morph)>>layoutInBounds: PaginatedMorphTreeMorph(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 PanelMorph(Morph)>>submorphBounds in Block: [:m | | subBox | m visible... Array(SequenceableCollection)>>do: PanelMorph(Morph)>>submorphBounds PanelMorph(Morph)>>privateFullBounds PanelMorph(Morph)>>doLayoutIn: PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: [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@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/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 111 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: 111; 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

1
0
0 0

Issue 943 in moose-technology: Integrate Rubric in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 943 by tu...(a)tudorgirba.com: Integrate Rubric in Glamour http://code.google.com/p/moose-technology/issues/detail?id=943 Rubric can be found at: Gofer new url: 'http://www.smalltalkhub.com/mc/AlainPlantec/Rubric/main'; package: 'Rubric'; load. In particular, we should integrate RubScrolledTextMorph and RubTextFieldMorph. -- 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
3
0 0

an stable Moose version for pharo2 ?

by Guillermo Polito

Hi guys, I was building a simple CI job to run an acceptance test for the pharovm. Now, as we talked with Esteban and Camillo, we want to: - take an stable pharo20 - load an stable freezed version of moose - load an stable freezed version of seaside - run tests as a first attempt. However, I find the configuration of moose has no 4.8 version as I was expecting, and loading the latest development version does not really do it (we want to test the vm, not moose :). How can I get a freezed version of moose working on 2.0? Tx!! Guille

12 years

3
3
0 0

moose 4.8

by Tudor Girba

Hi, As soon as all tests are green, we will release 4.8. The target would be end of next week at the latest. Afterwards, we move to Moose 5.0 on top of Pharo 3.0. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years

5
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev