Summary: Roassal should support lazy edges when used through the Mondrian
Labels: -Component-Mondrian Component-Roassal
Comment #10 on issue 113 by tu...(a)tudorgirba.com: Roassal should support
lazy edges when used through the Mondrian API
No, it does not. But, it should.
The idea is that the following Mondrian script should work:
view edge: #edge from: 1 to: 2.
view node: 1.
view node: 2.
For this, the edge creation should be evaluated only after all nodes are
I changed the entry title and labels.
Labels: Type-Defect Priority-Medium
New issue 772 by google....(a)ben.coman.com.au: Moose Panel > ST importer >
incorrect selection highlighting
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
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
6. In the [Selection] tab, selected "AST-Semantic" and clicked the
The row below that - "AST-Semantic-Binding" - is now highlighted as
7. Try to get rid of the selection highlighting on "AST-Semantic-Binding"
Labels: Type-Enhancement Priority-Medium Usability
New issue 732 by tudor.gi...(a)gmail.com: Moose should improve the visuals
for larger fonts
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.
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
Labels: Type-Defect Priority-Medium
New issue 771 by santiago...(a)gmail.com: Problem with tabs in Glamour
Running the following script:
| browser |
browser := GLMTabulator new.
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;
a text titleIcon: GLMUIThemeExtraIcons glamorousAdd; display:'add
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.