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
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
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
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.
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.
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.
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
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.
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
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
Hello,
i am experimenting with the Spy framework (i hope this is the appropriate
newsgroup).
I encountered the following problem:
Running unit tests through Spy gives sometimes other test results than
running them with the Test Runner.
I first encountered this problem when i tried in Pharo 2:
Profiler runTestsForPackages: #('XML-Parser-Nodes' 'XML-Tests-Parser-Nodes')
When the same tests are run from the Test Runner all 126 tests pass,
test results in the Spy Profiler show 12 failures.
Is anybody working with tests in Spy? Does anybody have an idea what may
cause this phenomenon and how to fix it?
Best regards,
Martin.
<http://forum.world.st/file/n4722052/Tests_with_Spy.png>
--
View this message in context: http://forum.world.st/Spy-alters-some-test-results-tp4722052.html
Sent from the Moose mailing list archive at Nabble.com.
Hi!
I've just opened Moose and got quite surprised by the beauty of it. Nice fonts, nice white space.
One missing thing: the autocompletion which is not on tab :-)
Good job Doru!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Doru wrote:
>I need a bit of help with the issue of the SpecDebugger relying on the default inspector being implemented in Spec.
Hmm, one gets used to having a decent inspector. Going back to the Pharo 3 default is not funny…
The GTInspector might be a bit of an ugly duckling, but there really is a big bad-ass powerful swan
in there.
I strongly support the help request. And phd organization of course.
Stephan
The only sender of
MooseEntityState>cache: selector initializer: aBlock
^self
propertyAt: selector
ifAbsentPut: [aBlock cullValue: self entity]
is
MooseEntity>lookUpPropertyNamed: selector computedAs: aBlock
^self privateState cache: selector initializer: aBlock
all senders of which in the Moose 5 image are parameterless blocks.
Is anyone depending on the existence of the entity instVar
in MooseDefaultState (and accessors in MooseEntityState)?
When looking at the class comment on MooseEntity, I wonder
why the state has a back link.
Stephan
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-GlamorousToolkit Milestone-5.0
New issue 996 by tu...(a)tudorgirba.com: GTInspector should update the
presentations when a new one is added from inside
http://code.google.com/p/moose-technology/issues/detail?id=996
When browsing the methods in the inspector, we can add a new method with a
presentation. When this happens, we want to inspector to refresh so that
the presentation appears on top.
--
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
Hi!
I like the way Moose is shaking.
What about the Moose association? Who is willing to accept some money?
Is there a subscription? What are the fees? How the money will be spent?
Is there a logo Object Profile can put on the website to say it is part of the Moose Association?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Does anyone know about this tool?
http://www.xtran-llc.com/index.html
It also promises a meta-tool for software engineering and some software
analysis and transformation services already built in the tool.
regards,
Usman
Hi everyone.
For me it’s still not clear how does HISMO version versions :).
To help myself explain my question I’ve attached the image.
What happens if a new nodes are added to each version. Do all 3 snapshots share same nodes, or they are duplicated? Because when I look at MooseSampleData>>initialization it seams to me that 5 different models are created and references to them are stored to them from history.
Cheers.
Uko
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.9
New issue 986 by tu...(a)tudorgirba.com: Roassal Athens uses the default
Morph logic for PNG export
http://code.google.com/p/moose-technology/issues/detail?id=986
Even though Athens can render with nice anti aliasing, when exporting to
PNG, the default logic is being used:
ROMorphicPlatform>>imageExporterClass
^ ROPharoImageExporter
We should use the nice rendering of Athens for the export.
--
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
Hi everyone.
Probably I’ve missed something, but how does it work in a way that when you select “All methods” in MooseFinder you get a FAMIXMethodGroup, and not just a MooseGroup? I’ve checked all the methods of FAMIXMethodGroup and all references to FAMIXMethodGroup, but I can’t figure it out.
Cheers
Uko
Hi guys
on my moose image the repo of Famix-Core is Moose/main and not Moose/Famix/main
and I'm confused because on smalltalkhub it is Moose/Famix/main
Help please :)
Stef
Martín wrote:
>I'm interested in the current state of your migration of Torch. Any news after this email?
I haven’t looked further. Blocked at the changes in AST-Semantic. I didn’t understand
what the replacement code in OPAL is supposed to be, and didn’t get enough
detailed responses then.
Stephan.