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 := GLMTabulator new.
tmpBrowser row: #list.
tmpBrowser transmit to: #list; andShow: [:a |
display: [:input | input];
tmpBrowser openOn: #( b c d v a d f r).
but the list still open with nothing selected
Labels: Type-Defect Priority-Medium Component-SmalltalkImporter
New issue 514 by tudor.gi...(a)gmail.com: Introduce the PharoImageSourceAnchor
Currently, FAMIXClass>>sourceText has a hack that checks for mooseModel
isSmalltalk explicitly. We should introduce a PharoImageSourceAnchor that
properly takes care of this.
Labels: Type-Defect Priority-Medium Milestone-4.3 Component-Famix
New issue 528 by jannik.l...(a)gmail.com: Remove Category Importer
With RPackage, Category importer is useless,
We should remove it.
They are some referecnes in examples in DSM.
Labels: Type-Defect Priority-Medium
New issue 648 by cy.delau...(a)gmail.com: improve overview pyramid
Overview pyramid should use colors so that we can easily read the different
Maybe also change the color code (green / blue / red for now.)
Labels: Type-Defect Priority-Medium RPackage
New issue 621 by stephane...(a)gmail.com: writing tests for removeMethod
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 "
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
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