Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 998 in moose-technology: VerveineJ: Method in EnumValue -> anonymous or inner class
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 998 by anne.et...(a)gmail.com: VerveineJ: Method in EnumValue -> anonymous or inner class http://code.google.com/p/moose-technology/issues/detail?id=998 Consider the following Java code (real one, got from FindBugs plugin). There are some method definitions in Enum Value. How VerveineJ should consider the enum values? as anonymous or inner classes? If it is inner classes the definition of innerClass method has to be modified since it considers only that the container is a class (and not a type). enum FilterKind { INCLUDE("property.includefilter") { Collection<String> selectedFiles(UserPreferences u) { return u.getIncludeFilterFiles(); } Collection<String> excludedFiles(UserPreferences u) { return u.getExcludeFilterFiles(); } void setFiles(UserPreferences u, Collection<String> files) { u.setIncludeFilterFiles(files); } }, EXCLUDE("property.excludefilter") { Collection<String> selectedFiles(UserPreferences u) { return u.getExcludeFilterFiles(); } Collection<String> excludedFiles(UserPreferences u) { return u.getIncludeFilterFiles(); } void setFiles(UserPreferences u, Collection<String> files) { u.setExcludeFilterFiles(files); } }, EXCLUDE_BUGS("property.excludebugs") { Collection<String> selectedFiles(UserPreferences u) { return u.getExcludeBugsFiles(); } Collection<String> excludedFiles(UserPreferences u) { return Collections.emptyList(); } void setFiles(UserPreferences u, Collection<String> files) { u.setExcludeBugsFiles(files); } }; final String propertyName; FilterKind(String propertyName) { this.propertyName = propertyName; } abstract Collection<String> selectedFiles(UserPreferences u); abstract Collection<String> excludedFiles(UserPreferences u); abstract void setFiles(UserPreferences u, Collection<String> files); } Additional information: platform, context which may impact the problem Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX -- 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

3 3

Issue 997 in moose-technology: Inspector: "MenuModel(Object)>>doesNotUnderstand: #add:target:selector:"
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 997 by anne.et...(a)gmail.com: Inspector: "MenuModel(Object)>>doesNotUnderstand: #add:target:selector:" http://code.google.com/p/moose-technology/issues/detail?id=997 Describe the problem: what do you get? what do you expect? MenuModel(Object)>>doesNotUnderstand: #add:target:selector: when using the inspector in Moose-5.0 How to reproduce the problem: step by step if necessary Open an image. Execute a piece of code (in a workspace for example) and inspect the result. If the result is an entity (and not a collection), right clic on an element of the left column (but neither the class nor the all inst vars). A pop up window with MenuModel(Object)>>doesNotUnderstand: #add:target:selector: appears. So it is not possible to use the inspector in Moose 5.0 Additional information: platform, context which may impact the problem I tried only on Mac Please fill in the labels with the following information: Type-Defect, Component-5.0 -- 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 1

Issue 1001 in moose-technology: Pharo: Moose: unable to get information from Dr. Geo packages.
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1001 by matttbe: Pharo: Moose: unable to get information from Dr. Geo packages. http://code.google.com/p/moose-technology/issues/detail?id=1001 Hello, First, thank you for developing this free and OpenSource platform! > Describe the problem: what do you get? what do you expect? With the latest version of the Moose Suite, I'm not able to analyse data from Dr. Geo packages: the Moose panel is empty. > How to reproduce the problem: step by step if necessary From Moose Suite 4.9 image and Pharo 2: * Install DrGeo with these commands: Gofer new url: 'http://www.squeaksource.com/DrGeoII' ; package: 'ConfigurationOfDrGeo'; load. (Smalltalk at: #ConfigurationOfDrGeo) perform:#load. * Open the Moose Panel / st / select all DrGeoII-* packages / Next / Finished * Select the new model: there is nothing in the panel! Here is a http://uppix.com/f-Capture_du_2013_5284a4e800148d17.png > Additional information: platform, context which may impact the problem I also tested with another image where Moose was already installed but I have the same problem. I'm using Pharo 2 on Linux but it seems that we also have this problem when using it on Windows. Note that I was able to have something in Moose Panel by doing that: * Open the Moose Panel / st / select random packages (e.g. I tried with PetitParser* packages) / Next / Finished * Select the new model: everything seems fine * Don't close the Moose Panel and install Dr. Geo from the workspace * Switch to the Moose Panel window / st / select DrGeoII-* packages / Next / Finished * Select this new model: we can see boxes and select lines but all graphs are empty! Feel free to ask if you need additional information! Thank you for your help, Matt -- 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 4

Issue 658 in moose-technology: write a test for MooseMenu entries
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 658 by jannik.l...(a)gmail.com: write a test for MooseMenu entries http://code.google.com/p/moose-technology/issues/detail?id=658 We need a test that take all entries in Moose Browser and test them, to avoid DNU and other kind.

1 4

Issue 728 in moose-technology: VerveineJ places methods in the wrong classes
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- CC: stephane...(a)gmail.com, anquetil...(a)gmail.com, usman.bh...(a)gmail.com Labels: Type-Defect Priority-Critical Component-VerveineJ New issue 728 by tu...(a)tudorgirba.com: VerveineJ places methods in the wrong classes http://code.google.com/p/moose-technology/issues/detail?id=728 For some reason, some methods are placed in the wrong classes. I did not manage to identify a standalone case, but it looks like if we have a case like below: public class A { ... public void m() { ... x() } } public class B { public void x() { ... } } public class C { ... } we sometimes get x as belonging to class C instead of B. The interesting part is that the invocation will go from A::m() to C::x(). This is a critical issue that stops us from using VerveineJ because the information is too unreliable.

5 18

Issue 704 in moose-technology: One click image has a squeak icon
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 704 by alexandr...(a)gmail.com: One click image has a squeak icon http://code.google.com/p/moose-technology/issues/detail?id=704 Apparently, the icon of the one-click image available form Moose;s jenkins is the Squeak one.

1 4

about white theme
by Stéphane Ducasse 14 Nov '13

14 Nov '13

Hi guys probably this has been fixed. I'm coding in a Moose 4.8 with the (old?) white theme and this is really bad because on the screen I used I cannot see the separation between widgets. This lost of space border is a pain. So I now use the blue theme. Stef

2 1

Issue 837 in moose-technology: ROCircle not constrained to equal dimensions
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 837 by google....(a)ben.coman.com.au: ROCircle not constrained to equal dimensions http://code.google.com/p/moose-technology/issues/detail?id=837 Currently ROCircle acts more like a hypothetical ROEllipse, since it is not constrained to force dimensions to be equal. The following might be a worthwhile test case... --- | rawView element1 element2 | element1 := (ROElement on: '1' ). element1 + ROCircle. element1 width: 200; height: 100. self assert: ( element1 height = 200). element2 := (ROElement on: '2' ). element2 width: 200; height: 100. element2 + ROCircle. "Swapped order with above line" self assert: ( element2 height = 200). "Should be true. Currently not." "optional - following not part of test - just visual feedback" rawView := ROView new. rawView add: element1. rawView add: element2. ROVerticalLineLayout on: rawView elements. rawView open. --- The first assert can be made to work by adding the following... ---- ROCircle>>extent: anExtentPoint | max | max := anExtentPoint x max: anExtentPoint y. extent := max @ max. next extent: anExtentPoint --- The second assert, I'm not sure yet about resolving the fail.

1 3

how to get a moose model shown in the moose finder
by Stéphane Ducasse 14 Nov '13

14 Nov '13

Hi guys I'm going over the tutorial that andre did to add XML in Moose and I have | xmlDoument visitor mooseModel| mooseModel := MooseModel new. mooseModel name: 'XML-Tests'. visitor := XMLNodeVisitor new mooseModel: mooseModel. xmlDoument := XMLDOMParser parse: XMLExamples shiporderXMLDoc. xmlDoument accept: visitor. Now I thought that all the models would be shown in the moose finder but this is not the case. How do I properly add a model there? Stef

3 3

Doing a pass over the tutorial and implementation of XMLFamix
by Stéphane Ducasse 14 Nov '13

14 Nov '13

Hi guys I'm doing a pass over the XML FAMIX tutorial that andre wrote a couple of years ago. I'm improving the text, the ppt support and updating the code to load in latest Moose (filesystem) Now I'm wondering if we should publish it in the Moose directory on Smalltalkhub because right now it is in the folder of andre. Andre what do you think? For me I would prefer to have everything in the same place. Now could you give me access to your repo? Stef

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev