Hi!
Since some of you are working on remodularizing code, maybe the following may inspire you.
In Mondrian, the tests are badly structured. I actually wrote a large part of them as a way for me to understand the initial version of Mondrian, back in 2007-2008. Most of the tests are contained in the class MOViewRendererTest. They actually contain a lot of duplicated scenario (not really code): I open a canvas, put some nodes and edges, run the layout...
I would like to cut this class into smaller unit tests. Fixture will have to be found for each new unit tests. How to structure them? Along the class hierarchy? Along the features of Mondrian? Along the features commonly used in Mondrian scripts (which is how they are roughly structured)?
I can remodularize my tests and come up with a satisfactory design in a couple of hours. But maybe someone worked on a tool that would help me on this.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
i got a strange behaviour from Mondrian trying to build a shape for data base tables. Basically defining a shape which contains a rectangle with a title and a children shape it happen that the rectangle containing the title have the same size of the children shape. Is it a bug or is a problem of my code? Below the code that i use, copy and paste in MOShapeSelector the tableShape method and than in a normal mondrian easel window you should be able to reproduce the same behaviour with the snippet below.
By using this shape definition:
tableShape
| builder |
builder := MOFormsBuilder new.
builder column; fill; pref; grow.
builder row; fill; pref; grow; row; fill; pref; grow.
builder x: 1 y: 1 add: (MORectangleShape new text: [:table | table name]; fontSize: 10).
builder x: 1 y: 2 add: MORectangleShape new.
builder x: 1 y: 2 add: MOChildrenShape new.
^view shape: builder shape
and using this visualization script:
view shape tableShape.
view node: (FAMIXNamedEntity new name: 'test') forIt: [
view shape rectangle.
view nodes: (1 to: 20).
view verticalLineLayout. ].
I got the result in the attachment.
Thanks,
Fabrizio
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 498 by fabrizio...(a)gmail.com: the sizes of the rectangles into
built shape are the same
http://code.google.com/p/moose-technology/issues/detail?id=498
Defining a shape which contains a rectangle with a title and a children
shape it happen that the rectangle containing the title have the same size
of the children shape while i would expect that the rectangle size was
coherent with its content.
By executing the following code in Mondrian you will see the problem
| builder |
builder := MOFormsBuilder new.
builder column; fill; pref; grow.
builder row; fill; row; fill; pref; grow.
builder x: 1 y: 1 add: (MORectangleShape new text: [:table | table name];
fontSize: 10).
builder x: 1 y: 2 add: MORectangleShape new.
builder x: 1 y: 2 add: MOChildrenShape new.
view shape: builder shape.
view node: 'hello' forIt: [
view nodes: (1 to: 5).
view verticalLineLayout
]
Updates:
Labels: -Component-Verveine Component-VerveineJ
Comment #1 on issue 480 by tudor.gi...(a)gmail.com: VerveineJ: file-anchor
contains absolute path
http://code.google.com/p/moose-technology/issues/detail?id=480
(No comment was entered for this change.)
Status: New
Owner: georgega...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-ExternalTools
New issue 531 by tudor.gi...(a)gmail.com: inFusion should export isWrite in
FAMIXAccess
http://code.google.com/p/moose-technology/issues/detail?id=531
If it represents an assignment it should look like:
(FAMIX.Access
(isWrite true)
)
Hi!
I am ready to continue working on the Fuel extension for binary
export/import in Moose.
I am working on:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
Tasks:
- create ConfigurationOfFuel with a default config
- fix an error running tests (I thin the problem raises because now
I'm on Windows, not MacOs)
- fix a buf found by Doru last time: "a bug with FAMIXAccess that when
the isWrite flag was nil, isRead would raise an error (it is fixed in
the meantime). This appeared when I exported the model with MSE, but
it did not appear when I used Fuel".
- fix the icon for Fuel import in MoosePanel.
Is this ok?
Cheers,
Martin
Hi,
I marked as broken the 4.3* versions from ConfigurationOfMoose and 2.* versions of SmallDude, and now the default version of ConfigurationOfMoose loads fine again.
While this fixes the situation now, we still have to fix the overall problem of properly packaging of projects.
So, to this end, I propose to keep ConfigurationOfMoose only load the Core of Moose + the generic engines, and create a ConfigurationOfMooseSuite that will include all the other tools that extend FAMIX like SmallDude and DSM.
Also, we will have to take a look at factoring out the generic parts of the DSM and SmallDude engines and make a clear separation from the FAMIX specific code. In DSM this happens quite well already, but we need to look into it again and probably move the CycleTable & co to MooseAlgos.
Cheers,
Doru
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
Hi,
I just installed latest glamour in a pharo 1.2.
I creating a browser with a magritte presenter, and the magritte component doesn't fill the panel. This is the code:
buildBrowser
| browser |
browser := GLMTabulator new
title: 'Builder';
row: #navigation;
row: #edition;
yourself.
browser transmit
to: #navigation;
andShow: [ :presenter |
presenter finder
show: [ :eachPresenter |
eachPresenter list
title: [ :each | each asString ];
when: [ :each | each respondsTo: #allParticipants ];
display: #allParticipants.
eachPresenter label
when: [ :each | (each respondsTo: #allParticipants) not ] ] ].
browser transmit
from: #navigation;
to: #edition;
andShow: [ :presenter |
presenter magritte
title: [ :each | each asString ] ].
^browser
A screenshot of the result:
Any idea?
Cheers,
Esteban
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Glamour
New issue 546 by tudor.gi...(a)gmail.com: Searching in a Glamour list should
offer a progressbar
http://code.google.com/p/moose-technology/issues/detail?id=546
It should be easy to add a progressbar in the selection block.