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