March 2012 - Moose-dev

[Glamour] default selection in ListPresentation
by Cyrille Delaunay 24 Mar '18

24 Mar '18

Hello, Is there a way to set a default selection to a list presentation? so that when I open the browser, the morphic list has already a value selected. I tried that: |tmpBrowser| tmpBrowser := GLMTabulator new. tmpBrowser row: #list. tmpBrowser transmit to: #list; andShow: [:a | a list display: [:input | input]; selection: #a; yourself ]. tmpBrowser openOn: #( b c d v a d f r). but the list still open with nothing selected

3 4

Issue 514 in moose-technology: Introduce the PharoImageSourceAnchor
by moose-technology＠googlecode.com 13 Nov '14

13 Nov '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-SmalltalkImporter Component-Famix New issue 514 by tudor.gi...(a)gmail.com: Introduce the PharoImageSourceAnchor http://code.google.com/p/moose-technology/issues/detail?id=514 Currently, FAMIXClass>>sourceText has a hack that checks for mooseModel isSmalltalk explicitly. We should introduce a PharoImageSourceAnchor that properly takes care of this.

1 1

Issue 528 in moose-technology: Remove Category Importer
by moose-technology＠googlecode.com 12 Nov '14

12 Nov '14

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.3 Component-Famix Component-SmalltalkImporter New issue 528 by jannik.l...(a)gmail.com: Remove Category Importer http://code.google.com/p/moose-technology/issues/detail?id=528 With RPackage, Category importer is useless, We should remove it. They are some referecnes in examples in DSM.

1 6

Re: Issue 228 in moose-technology: Nested browsers do not take "when", or "display" into account
by moose-technology＠googlecode.com 24 Jul '14

24 Jul '14

Updates: Labels: -Milestone-4.2 Comment #4 on issue 228 by tudor.gi...(a)gmail.com: Nested browsers do not take "when", or "display" into account http://code.google.com/p/moose-technology/issues/detail?id=228 (No comment was entered for this change.)

1 1

Issue 757 in moose-technology: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder
by moose-technology＠googlecode.com 23 Jul '14

23 Jul '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 757 by tudor.gi...(a)gmail.com: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder http://code.google.com/p/moose-technology/issues/detail?id=757 Try this: GLMFinder new show: [:a | a smalltalkCode ]; openOn: ''. and then type "1 as". You will see that the completion appears in the top right of the world, instead of the top right of the text pane. This only happens in the finder, and it is likely due to some problems of transforming coordinates.

2 3

Issue 648 in moose-technology: improve overview pyramid
by moose-technology＠googlecode.com 22 Apr '14

22 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 648 by cy.delau...(a)gmail.com: improve overview pyramid http://code.google.com/p/moose-technology/issues/detail?id=648 Overview pyramid should use colors so that we can easily read the different results. Maybe also change the color code (green / blue / red for now.)

1 6

Issue 709 in moose-technology: add Moose-Eclipse-Plugin in Moose
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 709 by jannik.l...(a)gmail.com: add Moose-Eclipse-Plugin in Moose http://code.google.com/p/moose-technology/issues/detail?id=709 I don't know if we integrate it in Moose. But we need to do something: a web page on the Moose site, with how to load it.

1 3

Re: Issue 156 in moose-technology: The table presentation for Glamour should provide dynamic sorting and column manipulation
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Updates: Summary: The table presentation for Glamour should provide dynamic sorting and column manipulation Comment #14 on issue 156 by tudor.gi...(a)gmail.com: The table presentation for Glamour should provide dynamic sorting and column manipulation http://code.google.com/p/moose-technology/issues/detail?id=156 (No comment was entered for this change.)

1 1

Re: Issue 254 in moose-technology: inFusion default initializer export to MSE
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Updates: Labels: -Component-Tools Component-ExternalTools Comment #1 on issue 254 by tudor.gi...(a)gmail.com: inFusion default initializer export to MSE http://code.google.com/p/moose-technology/issues/detail?id=254 (No comment was entered for this change.)

1 2

Issue 690 in moose-technology: Change the font size of labels in a chart
by moose-technology＠googlecode.com 09 Jan '14

09 Jan '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee New issue 690 by andreho...(a)gmail.com: Change the font size of labels in a chart http://code.google.com/p/moose-technology/issues/detail?id=690 Change the font size of labels in a chart using #defaultFontSize: is not working.

1 2

Re: Issue 735 in moose-technology: OverviewPyramid raises Zero Divide
by moose-technology＠googlecode.com 05 Dec '13

05 Dec '13

Updates: Summary: OverviewPyramid raises Zero Divide Comment #4 on issue 735 by tudor.gi...(a)gmail.com: OverviewPyramid raises Zero Divide http://code.google.com/p/moose-technology/issues/detail?id=735 (No comment was entered for this change.)

1 2

Issue 772 in moose-technology: Moose Panel > ST importer > incorrect selection highlighting
by moose-technology＠googlecode.com 20 Nov '13

20 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 772 by google....(a)ben.coman.com.au: Moose Panel > ST importer > incorrect selection highlighting http://code.google.com/p/moose-technology/issues/detail?id=772 Upon removing an item from a list, the next item down becomes higlighted like it is selected and the highlighting cannot be removed. It is not really selected. How to reproduce the problem: 1. Unzipped Moose Suite 4.6 Development 2. Ran Moose.app\Contents\Windows\Squeak.exe 3. WorldMenu > Moose > Moose Panel 4. Clicked the ST downarrow icon. (btw, you might think about giving the dialog that pops up a title) 5. In the [Initial list] tab selected the nine "AST-*" entries and clicked the three-right-arrows. 6. In the [Selection] tab, selected "AST-Semantic" and clicked the three-left-arrows. The row below that - "AST-Semantic-Binding" - is now highlighted as selected. 7. Try to get rid of the selection highlighting on "AST-Semantic-Binding"

1 1

Issue 732 in moose-technology: Moose should improve the visuals for larger fonts
by moose-technology＠googlecode.com 17 Nov '13

17 Nov '13

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Usability New issue 732 by tudor.gi...(a)gmail.com: Moose should improve the visuals for larger fonts http://code.google.com/p/moose-technology/issues/detail?id=732 The icons from GLMUIThemeExtraIcons and from MooseIcons should be saved in larger resolutions (currently, they are in 16x16). Mondrian should offer a default class variable for the size of nodes and the width of nodes and edges. These should be settable via global settings.

1 2

Re: Issue 362 in moose-technology: Add commands to create/delete Hismo models
by moose-technology＠googlecode.com 17 Nov '13

17 Nov '13

Comment #5 on issue 362 by alexandr...(a)gmail.com: Add commands to create/delete Hismo models http://code.google.com/p/moose-technology/issues/detail?id=362 In Moose-Hismo-AlexandreBergel.57 , you can now delete an hismomodel. We need a way to create an hismo model

2 2

Issue 666 in moose-technology: package name in DSM
by moose-technology＠googlecode.com 17 Nov '13

17 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-DSM New issue 666 by jannik.l...(a)gmail.com: package name in DSM http://code.google.com/p/moose-technology/issues/detail?id=666 The package name in DSM, specially in encaps DSM are not well placed.

1 3

Issue 621 in moose-technology: writing tests for removeMethod
by moose-technology＠googlecode.com 17 Nov '13

17 Nov '13

Status: Accepted Owner: ---- CC: cy.delau...(a)gmail.com Labels: Type-Defect Priority-Medium RPackage New issue 621 by stephane...(a)gmail.com: writing tests for removeMethod http://code.google.com/p/moose-technology/issues/detail?id=621 writing tests for "The bug appeared when removing two extensions methods (from the same extending package) for a same class. in RPackage >> removeMethod: , when removing an extension method, we were telling the organizer to remove the extending package for the class concerned. This was wrong, because even if one extension from this package has been removed, some others can still exist. And the organizer should keep the this package as extending package for the class. So removing the first extension method worked correctly, but then removing a second or more methods from the same package was raising some errors "

1 4

Issue 527 in moose-technology: Add ModelInfo to hold extra information in MSE
by moose-technology＠googlecode.com 17 Nov '13

17 Nov '13

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-MooseCore Milestone-4.3 New issue 527 by tudor.gi...(a)gmail.com: Add ModelInfo to hold extra information in MSE http://code.google.com/p/moose-technology/issues/detail?id=527 We should add a special MooseModelInfo entity that can be serialized in MSE. Like this we would have a backward compatible solution for storing extra information in MSE such as: - source language - importer version - metamodel version - importing date - source version I will give it a try for 4.3

1 2

Issue 771 in moose-technology: Problem with tabs in Glamour
by moose-technology＠googlecode.com 17 Nov '13

17 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 771 by santiago...(a)gmail.com: Problem with tabs in Glamour http://code.google.com/p/moose-technology/issues/detail?id=771 Running the following script: | browser | browser := GLMTabulator new. browser row: [ :r | r column: #columnA; column: #columnB ]. browser transmit to: #columnA; andShow: [ :a | a list display: [" :model | "#('Value 1' 'Value 2' 'Value 3' 'Value 1') ] ]. browser transmit from: #columnA; to: #columnB; andShow: [ :a | a list titleIcon: GLMUIThemeExtraIcons glamorousBrowse; display:#('data A' 'data B' 'data C'). a text titleIcon: GLMUIThemeExtraIcons glamorousAccept; display:'something'. a text titleIcon: GLMUIThemeExtraIcons glamorousAdd; display:'add something'. ]. browser openOn: MooseModel root allModels anyOne. after selecting a value in columnA the columnB is opened in the last tab (the one with the glamorousAdd icon). Instead it must be opened in the first tab (the one with the glamorousBrowse icon). Using text instead of icons, it works.

2 3

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

Re: Issue 435 in moose-technology: Using RoelTyper for a better precision of method invocation
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Updates: Labels: Component-SmalltalkImporter Comment #4 on issue 435 by tudor.gi...(a)gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435 It seems that RoelTyper does not work for all classes. Try this code for getting the classes that raise an error: classes := Dictionary new. Object withAllSubclassesDo: [:each | [(TypeCollector typeInstvarsOfClass: each )] on: Error do: [:error | classes at: each put: error ]]. classes inspect

1 5

Issue 516 in moose-technology: System Complexity displays more than the classes in the group
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 516 by tudor.gi...(a)gmail.com: System Complexity displays more than the classes in the group http://code.google.com/p/moose-technology/issues/detail?id=516 Currently, the algorithm to identify the hierarchies does not limit the result to the current class group, but it takes all the subclasses of the superclass. This means that if you have a group with Object inside, you will end up with a system complexity with all classes.

1 4

Issue 526 in moose-technology: Add explicit Interface in Famix
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Milestone-4.3 New issue 526 by tudor.gi...(a)gmail.com: Add explicit Interface in Famix http://code.google.com/p/moose-technology/issues/detail?id=526 We should have a FAMIXInterface.

1 6

Loading Hapax
by Hernán Morales Durand 06 Nov '13

06 Nov '13

Hello, I know that Hapax possibly isn't fully ported to Pharo, but running the Hapax tests causes my Moose 4.5 image to hang (I've loaded everything in the SqS Hapax repository). What image and package loading order should one use to load Hapax? I'm interested in the information retrieval part for natural language analysis, could that part be repackaged in its own package? Cheers, Hernán

6 12

Issue 714 in moose-technology: VerveineJ does not produce correct values for classes in annotation instances
by moose-technology＠googlecode.com 23 Aug '13

23 Aug '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-High Component-VerveineJ New issue 714 by tudor.gi...(a)gmail.com: VerveineJ does not produce correct values for classes in annotation instances http://code.google.com/p/moose-technology/issues/detail?id=714 Take a look at the example below: @XmlElement(name = "Time", required = true, type = String.class) protected Date time; The value of the third attribute of the annotation instance is the actual source code of the String class. Instead, it should be just the string 'String.class'. Ideally, we would get an actual reference, but the string would do for now.

2 11

Issue 686 in moose-technology: Order in the Mondrian view DSL?
by moose-technology＠googlecode.com 07 Jul '13

07 Jul '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 686 by step...(a)stack.nl: Order in the Mondrian view DSL? http://code.google.com/p/moose-technology/issues/detail?id=686 The order in which the view script has to be build up is not very clear. This is to be documented in http://www.themoosebook.org/book/internals/mondrian/scripting {shape, interaction} < nodes < edges * Type-Review * Component-Mondrian

1 2

Issue 716 in moose-technology: span or size for each column in GLMTablePresentation
by moose-technology＠googlecode.com 01 Jul '13

01 Jul '13

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 716 by jannik.l...(a)gmail.com: span or size for each column in GLMTablePresentation http://code.google.com/p/moose-technology/issues/detail?id=716 I am using GLMTablePresentation, and I would like to specify span or size for each column. To do that: Extend the GLMTablePresenation, and the associated rendering.

1 2

Issue 748 in moose-technology: DistributionMap examples not working
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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

1 3

Issue 555 in moose-technology: DSM improve visualization
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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.

1 2

Re: Issue 482 in moose-technology: Use JNIPort to connect to VerveineJ
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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.

2 4

Re: Issue 432 in moose-technology: Popup should appear only when a certain modifier key is pressed
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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.

1 8

Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

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.)

4 15

Issue 647 in moose-technology: Integrate torch package visualization
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

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…

2 4

Re: Issue 469 in moose-technology: integrate Kontractor
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

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?

1 3

Re: Issue 437 in moose-technology: Text is not affected by zooming in Mondrian
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

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

1 4

importers page
by Tudor Girba 28 Apr '13

28 Apr '13

Hi, I created a page dedicated to importing instructions: http://www.moosetechnology.org/docs/importers A good example of how these instructions should look like can be found here: http://www.moosetechnology.org/docs/importers/importJavaWithinFusion We would need more detailed information about: - Import C# with PMCS http://www.moosetechnology.org/docs/importers/importCSharpWithPMCS - Import C with CAnalyzer http://www.moosetechnology.org/docs/importers/importCWithCAnalyzer Cheers, Doru -- www.tudorgirba.com "Obvious things are difficult to teach."

7 14

Re: Issue 382 in moose-technology: CMD + W does not close Mondrian window
by moose-technology＠googlecode.com 16 Mar '13

16 Mar '13

Comment #1 on issue 382 by tudor.gi...(a)gmail.com: CMD + W does not close Mondrian window http://code.google.com/p/moose-technology/issues/detail?id=382 This is still an issue and it hinders usability. Alex, could you take a look at it?

1 1

Issue 784 in moose-technology: opposite is missing in FAMIXLacalVariable>>parentBehaviouralEntity
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 784 by fabrizio...(a)gmail.com: opposite is missing in FAMIXLacalVariable>>parentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=784 Hi, I figured that parentBehaviouralEntity was implemented like that: FAMIXLacalVariable>>parentBehaviouralEntity <MSEProperty: #parentBehaviouralEntity type: #FAMIXBehaviouralEntity> <MSEComment: 'Behavioural entity declaring this local variable. belongsTo implementation'> ^parentBehaviouralEntity The opposite is missing. Is there a reason for that? Shouldn't it be like: FAMIXLacalVariable>>parentBehaviouralEntity <MSEProperty: #parentBehaviouralEntity type: #FAMIXBehaviouralEntity opposite: #localVariables> <MSEComment: 'Behavioural entity declaring this local variable. belongsTo implementation'> ^parentBehaviouralEntity Cheers, Fabrizio

1 2

Issue 720 in moose-technology: Classic Coder should highlight the extension categories
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 720 by tudor.gi...(a)gmail.com: Classic Coder should highlight the extension categories http://code.google.com/p/moose-technology/issues/detail?id=720 Currently, only classes and methods are shown as extensions using gray. Categories should be grayed out as well.

1 2

Issue 640 in moose-technology: Get the axis labels in a lineDiagram
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 640 by andreho...(a)gmail.com: Get the axis labels in a lineDiagram http://code.google.com/p/moose-technology/issues/detail?id=640 Get the axis labels in a lineDiagram in not working. See example below: | diag factory | factory := ESDummyFactory new. factory yValues: #(22 25 13 16 24 28 35 24 32 24 46 12). factory identifiers: #('January' 'February' 'March' 'April' 'Mai' 'June' 'July' 'August' 'September' 'October' 'November' 'December'). diag := ESDiagramRenderer new. (diag lineDiagram) y: #yValue; width: 500; height: 400; lineWidth: 5; defaultFontSize: 12; identifier: #identifier; labels: [:each | each]; defaultColor: Color blue; yAxisLabel: 'Clients'; regularAxis; deviationValue: 22; deviationDescription: 'avg 2006'; models: factory buildDummies. "startLineAtZero;" ^ diag open

1 2

Issue 637 in moose-technology: VerveineJ should show an invocation to the default constructor
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 637 by tu...(a)tudorgirba.com: VerveineJ should show an invocation to the default constructor http://code.google.com/p/moose-technology/issues/detail?id=637 A call to the default constructor should be modeled like: - create a stub constructor in the target class - create an invocation to the constructor See the attached class for a sample. Attachments: DefaultConstructor.java 184 bytes

1 6

Issue 636 in moose-technology: VerveineJ should set hasClassScope
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 636 by tu...(a)tudorgirba.com: VerveineJ should set hasClassScope http://code.google.com/p/moose-technology/issues/detail?id=636 Static fields or methods should be marked with hasClassScope=true: public static int attributeWithClassScope; public static void methodWithClassScope() {} See the attached sample class. Attachments: ClassScope.java 179 bytes

1 3

Issue 781 in moose-technology: VerveineJ should mark getters setters and constants
by moose-technology＠googlecode.com 08 Dec '12

08 Dec '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 781 by santiago...(a)gmail.com: VerveineJ should mark getters setters and constants http://code.google.com/p/moose-technology/issues/detail?id=781 The property "kind" of the MSE models should be used to mark if a method is a getter, a setters or constant. Currently is only used to mark if a method is constructor

1 2

Issue 734 in moose-technology: VerveineJ does not export parameters for stub methods
by moose-technology＠googlecode.com 30 Nov '12

30 Nov '12

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 734 by tu...(a)tudorgirba.com: VerveineJ does not export parameters for stub methods http://code.google.com/p/moose-technology/issues/detail?id=734 If we analyze this code, the print method will appear without parameters. public class NoParametersInStubMethods { public void invoking() { System.out.print("aString"); } }

2 2

Issue 761 in moose-technology: Missing method invocation with VerveineJ
by moose-technology＠googlecode.com 30 Nov '12

30 Nov '12

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 761 by anquetil...(a)gmail.com: Missing method invocation with VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=761 see discussion on mailing list: "invokingMethods broken in moose or inFamix" source code: http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/ke… The method getLinkedEntityTypes in org.apache.stanbol.enhancer.engines.keywordextraction.linking.EntityLinker has an empty collection of invokingMethods even though the method is invoked for example by "process()".

3 4

Issue 762 in moose-technology: VerveineJ keeps the history of old entities, when invoked from the Moose interface
by moose-technology＠googlecode.com 27 Nov '12

27 Nov '12

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium New issue 762 by usman.bh...(a)gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762 First, I invoke VerveineJ from Moose menu to analyse a program A. It analyses the program and imports its entities in a moose model. I invoke VJ once more from moose menu to analyse another program B. When VJ is executed and the entities of program B are imported, I also find in the same model the entities related to the program A. So, VerveineJ keeps the history of old entities, when invoked from Moose interface. I think the problem can be resolved by deleting output.mse once VJ has finished its analysis and the entities are imported in a moose model.

2 9

Issue 746 in moose-technology: VerveineJ should create parameters for methods with different signatures
by moose-technology＠googlecode.com 26 Nov '12

26 Nov '12

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.6 New issue 746 by tu...(a)tudorgirba.com: VerveineJ should create parameters for methods with different signatures http://code.google.com/p/moose-technology/issues/detail?id=746 In some cases, calls to external libraries get reified as methods with proper signatures, but without parameters. I am trying to reproduce this using the following example (in ad_hoc/MultipleSignatures.java): package ad_hoc; import java.io.PrintWriter; import java.io.StringWriter; public class MultipleSignatures { public void callToRegularPrintStackTrace(Throwable t) { t.printStackTrace() } public void callToPrintStackTraceWithParam(Throwable t) { t.printStackTrace(new PrintWriter(new StringWriter())) } } I encountered a similar code in a case study. However, in this case, I cannot even get the parser to recognize both printStackTrace calls.

1 4

Issue 769 in moose-technology: Glamour should support drag and drop
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Milestone-4.6 Component-Glamour New issue 769 by tudor.gi...(a)gmail.com: Glamour should support drag and drop http://code.google.com/p/moose-technology/issues/detail?id=769 Something like this: a list allowItemDrag: [:item :list | ... ]; itemDrag: [:item :list | ... ] a list allowDropOnItem: [:draggedObject :targetItem :list | ... ]; dropOnItem: [:draggedObject :targetItem :list | ... ]

5 12

Issue 708 in moose-technology: Fame should accept comments both for properties and for meta descriptions
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MooseCore Milestone-4.6 New issue 708 by tudor.gi...(a)gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708 Currently, the MSEComment: is used to define comments of a property. SomeEntity>>someProperty <MSEProperty: ...> <MSEComment: 'comment'> This is used by the MetaBrowser but not by Fame. At the very least, we should add a means to add MSEComment: to the class side for the overall class.

1 5

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2012