Hi,
I refactor the logic of translateTo: and translateBy: in Mondrian. Now
translateTo: moves the element to the position by just delegating to
translateBy: with the difference from the current position.
I also added translateBy:bounded: to distinguish between the use case
of limiting the space when draggin and droping, while allowing it to
position anywhere during lay out.
This was important because I also upgraded a bit the
DominanceTreeLayout to position each level at the same y position so
that we can finally distinguish layers. I am saying finally because
this was always the goal of this layout :).
All tests are green, but in case you encounter problems, please let me
know.
Cheers,
Doru
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting
is the right one."
Hi Tudor,
I have updated my image with the latest version of Glamour and i encountered a problem...
when using mondrian and text presentations that include a title, the scrollbars are gone :S
if i removed the titles the scrollbars appear again, but in my browser with multiple columns and rows they are needed...
i even tried this in some examples (e.g. simpleMondrianPainting, textPortsExamples) and the same happens :(
regards,
Veronica Uquillas
Hi Doru,
I had two small ideas for Glamour:
- in a menu, it could be useful to have a method "addLine", like in MenuMorph, which integrate a line to separate two prt of a menu.
- is it possible to have a table-tree ? I think about a tree layout, with a table representation.
Another thing:
I like to pay with Glamour, thank you for your work :).
Cheers
---
Jannik Laval
---
Hi,
In the latest snapshot of Moose I found that FAMIXAbstractFile extends
FAMIXEntity. And furthermore it has no 'name' attribute.
Is this correct?
I would expect it to extend FAMIXNamedEntity.
This causes some problems when opening a model with file entities in Moose,
because they have no names.
Thanks,
Adrian Dozsa
Hi everyone,
Should it be possible to import mse files that were generated by the Visualworks version of Moose into the Pharo version of Moose ?
I tried and I am getting syntax errors.
If it's not possible, any ideas to make it work?
thanks!
----------------------------
Johan Brichau
johan.brichau(a)uclouvain.be
Hi Veronica,
This is really strange.
Please try with the latest Moose build image from here (based on
Pharo-1.0-10508-rc2):
http://hudson.moosetechnology.org/job/moose-latest-dev/39/artifact/moose/
Does it work?
Cheers,
Doru
On 7 Feb 2010, at 21:05, Veronica Uquillas Gomez wrote:
> HI Tudor,
>
> this is what i see :S
> i already tried in 2 images....
>
> will start over only loading glamour...
>
> Vero
>
>> And this time with attachment :)
>>
>> Doru
>>
>>
>
> <image.png>
--
www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Hi,
In the last version of Moose Finder, the models are selected by double
click not by click. This allows you to invoke the menu of a model
without necessarily having to select it. It also maps nicely on the
idea that a new tab is always created with double click (both from the
models list and from somewhere in the finder)
Also if you select a tab with a model, it selects the appropriate
model in the list. This is doable because now the accumulator
populates activeEntity with the entity behind the tab. You can see an
example at:
GLMBasicExamples new accumulator openOn: 42
It's actually pretty cool :).
Cheers,
Doru
--
www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
Hi Doru,
I begin to use GLMTablePresentation, it is really nice.
I try to use two possible features (which do not work):
- color:
- icon:
In fact, in the table, I would like to have a color for a line depending to a result.
For exemple, if a result is negated, the ine is highlighted in red, else it is in green.
In the same idea, (maybe, it is already possible), to have an icon to show an evolution of a value. For example, if a metric grows, put a "up" arrow.
Maybe these things are already implemented, or in progress.
I don't see them in example,
So maybe you want I create an issue for improvment ?
Cheers.
---
Jannik Laval
---
Hello Doru !,
I am showing a Mondrian drawing in a Glamour panel, and I am trying to
solve the following problems:
- When shown in a Glamour browser, how I could add to the Mondrian frame
a scroll bar ? the Mondrian visualizations are often larger than the
panel, and since there is not a scroll bar, they are shown incomplete
(when using Mondrian outside Glamour the scroll-bar is there when needed).
- In my Mondrian drawing, the nodes are not reacting to double-click
events that are configured. However, if I show the Mondrian drawing
outside glamour, double click events works fine.
- is there a way to visualize subtitles to the multiple panels that
compose my glamour browser ?. In addition, I never managed to change the
title of the browser (Glamorous Browser by default), even though -as a
test- I sent the "title:" message to the browser object and to every
object that could understand it, but without affecting the title when
the browser was shown.
this is the snippet of the code I am using for working with Mondrain in
Glamour:
browser
row:
[:row2 |
row2 column: #proofTree.
browser
showOn: #proofTree;
from: #proofNode;
using:
[| mond |
mond := browser mondrian.
mond painting: [:view :node | ... ]
...
]
thanks in advance for any help !
--
Sergio Castro
Département d'Ingénierie Informatique (INGI)
Université catholique de Louvain (UCL)
Belgium
okaaay, wrong reply-to, retweet....
Begin forwarded message:
> From: Simon Denier <Simon.Denier(a)inria.fr>
> Date: 28 janvier 2010 23:45:50 HNEC
> To: Simon Denier <Simon.Denier(a)inria.fr>
> Subject: Re: [Moose-dev] Building package cache
>
>
> On 26 janv. 2010, at 22:03, Simon Denier wrote:
>
>>
>> On 26 janv. 2010, at 21:07, Alexandre Bergel wrote:
>>
>>> I do not have a solution, but this is really annoying. In addition to the time taken by loading Moose, it makes 10 minutes just to check what are are dependencies Mondrian has.
>>>
>>
>> Well, temporary solutions sometimes become less than temporary... I fear this is the case.
>>
>> Maybe we can do something with an incremental, on-demand cache: whenever a class or method is imported, we check whether the cache has been built for it - if not, we built it.
>
>
>
> After playing a bit with the idea tonight, now I remember why I choose the global cache solution. So I explain how it works in the current system:
>
> To build the system cache, I go over all classes and all class extensions of PackageInfos and register their most specific package.
> Since I go over the whole system, I assume I know all class extensions in all classes.
> Now when I ask the package for a method, there are two cases:
> - either I can find it in the cache of class extensions and I return its package
> - either I can't find it, so I assume it is a normal method and retrieve the package of its class (from the cache).
>
> Now in an incremental cache system, I can cache a class when I import it, I can even cache a package so that its class extensions are imported, as above. The big problem is then that I can't assume that I know all class extensions within the class, because other packages (which I don't necessarily import) may do some. To do that, I should ask all methods within each imported class for its most specific package. This was more or less the situation we had before the cache, which brought the system to its knees on large projects. Perhaps I will try tomorrow but I don't have high hope. We need something better than that.
>
>
> --
> Simon
>
>
>
--
Simon
Hi Alex,
Is it possible to intégrate small fonts in Mondrian.
Alain Plantec has made a package named 'DejaVue' published in squeaksource.
It would be great to integrate it in Mondrian.
Cheers
---
Jannik Laval
---
Hi,
yesterday I tried to delete a moose model from my image using the function Utilities>>Delete on the moose panel. The model disappear from the list but saving the image it has the same size. Executing "MooseModel allInstances" I saw that the model was still there. I tried to close all windows and then i execute "Smalltalk garbageCollect" and again the saved image has the same size because the model has not been removed.
I'm working on the pharo dev image 10508, Moose-Core 215 but i detect the same error in an older image: pharo dev image 10502, Moose-Core 208.
Cheers,
Fabrizio
Hi Jannik,
Sometimes the DSMMatrixTest>>testSorterLayer test is failing. Do you
happen to have an idea why? Is it a problem of the code or is it
actually a problem of the test?
I am asking because it is the only test that crashes from time to time
in the hudson builds :).
Cheers,
Doru
--
www.tudorgirba.com
"Being happy is a matter of choice."
Hi there
Issue 28 is now closed. It was the last pending issue for 4.0 in Moose itself. Tests are green in Moose and we add another test for the case. So you should not notive any problem when running the importer.
--
Simon & Stef
In xml files generated with srcml, we can find the balise '<decl_stmt>..
</decl_stmt>'. Does anyOne know what it represent? Because I have the
impression that it represent sometimes a function declaration, But this is
not assimilate to a function declaration in CAnalyzer.
Hi,
When opening a mooseModel in a mooseFinder, several groups of entities
appear ('all famixaaccess' 'all famixattribute'). How can I access to this
groups from the mooseModel.
I have tryed to send 'entityGroups' to a moose model (generated with
CAnalyzer) , but it only answer me a part of all the groups visible.
Hi Alex,
Thanks for implementing the zOrder! It works great.
What's even nicer is that in the process, it looks like issue the edge
clipping problem was also solved:
http://code.google.com/p/moose-technology/issues/detail?id=229
Cheers,
Doru
--
www.tudorgirba.com
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
It should now be okay. Please update to
Mondrian-Alexandre_Bergel.355
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Let's continue the discussion on the mailing list.
Yesterday evening I imeplemented zOrder. Howerver, I haven't detected
any noticiable slowdown. Here is the health report I just produced. I
use a 10508 image. Execute: MondrianHealth new produceReport
Do you have similar figures ? (I have a MacBook Pro).
Report produced on 2010-01-27T07:19:43+00:00
Benchmark ManyNode (simple rendering of nodes) :
100 nodes => 2 ms
200 nodes => 4 ms
300 nodes => 6 ms
400 nodes => 7 ms
500 nodes => 9 ms
600 nodes => 11 ms
700 nodes => 13 ms
800 nodes => 14 ms
900 nodes => 15 ms
1000 nodes => 18 ms
1600 nodes => 29 ms
Benchmark ManyEdges (simple rendering of edges) :
10 edges => 1 ms
20 edges => 6 ms
30 edges => 14 ms
40 edges => 27 ms
50 edges => 49 ms
60 edges => 77 ms
70 edges => 118 ms
80 edges => 175 ms
90 edges => 348 ms
100 edges => 362 ms
200 edges => 5349 ms
300 edges => 43118 ms
54.77 % of methods are covered
Progress from last time: 0.0 %
On 27 Jan 2010, at 05:25, Laval Jannik wrote:
> Il fonctionne ici.
>
> Par contre, j'ai un comportement bizarre avec les derniers versions
> de Mondrian:
> Il est vraiment vraiment lent.
>
> Il devient impossible d'utliser DSM car très difficile de scroller
> ou meme d'afficher les popup:
> Pour afficher une popup, je dois attendre plus de 8 secondes....
> Bouger la fenetre ou l'agrandir est aussi difficile.
>
> J'utilise une 10508-dev toute clean que j'ai chargé ce matin.
>
> Jannik
>
>
> On Jan 27, 2010, at 01:41 , Alexandre Bergel wrote:
>
>> C'est vraiment bizarre. Le right-click ne m'offre pas de menu.
>> J'ai essayé de voir cela avec Doru, mais il n'arrive pas à
>> reproduire la chose.
>>
>> Alexandre
>>
>>
>> On 26 Jan 2010, at 11:33, Laval Jannik wrote:
>>
>>> sur all model packages dans moose,
>>> tu peux utliser DSM with Zoom.
>>>
>>> Dans la fenetre qui s'ouvre avec + et -, il y a normalement un
>>> refresh.
>>> Il fonctionne une premiere fois.
>>> Ensuite, il fonctionne seulement quand je selectionne une autre
>>> fenetre...
>>>
>>> Jannik
>>>
>>> On Jan 26, 2010, at 15:18 , Alexandre Bergel wrote:
>>>
>>>> Je suis en train de charger tout moose maintenant. Dis moi
>>>> comment je peux tester
>>>>
>>>> Alexandre
>>>>
>>>>
>>>> On 26 Jan 2010, at 11:15, Laval Jannik wrote:
>>>>
>>>>> Salut Alex,
>>>>>
>>>>> J'ai enlevé le code.
>>>>> Maintenant, il ne rafraîchi qu'une seule fois.
>>>>>
>>>>> Je ne comprends pas pourquoi.
>>>>>
>>>>> Jannik
>>>>>
>>>>> On Jan 23, 2010, at 15:15 , Alexandre Bergel wrote:
>>>>>
>>>>>> Enlève juste le code. Tu devrais quand meme avoir le refresh
>>>>>>
>>>>>> Alexandre
>>>>>>
>>>>>>
>>>>>> On 22 Jan 2010, at 08:51, Laval Jannik wrote:
>>>>>>
>>>>>>> Salut Alex,
>>>>>>>
>>>>>>> Pardon pour la réponse un peu tardive :)
>>>>>>>
>>>>>>> Oui c'est codé de cette façon :)
>>>>>>> Par contre, le code ne reconnait plus MorphicWindowAnnouncement.
>>>>>>>
>>>>>>> Y a-t-il un package particulier à charger ?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Jannik
>>>>>>>
>>>>>>> On Jan 16, 2010, at 00:52 , Alexandre Bergel wrote:
>>>>>>>
>>>>>>>> Hi!
>>>>>>>>
>>>>>>>> Juste pour info, si tu le code:
>>>>>>>> window announcer
>>>>>>>> on: MorphicWindowAnnouncement
>>>>>>>> do: [:ann | self root resetFormCacheResursively].
>>>>>>>>
>>>>>>>> que tu as dans openDSM, openDSMDemo et openDemo, cela devrait
>>>>>>>> marcher pareil.
>>>>>>>>
>>>>>>>> Alexandre
>>>>>>>> --
>>>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>>>>> Alexandre Bergel http://www.bergel.eu
>>>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>>>> Alexandre Bergel http://www.bergel.eu
>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> ---
>>> Jannik Laval
>>> PhD Student - Rmod Team - INRIA
>>> Certified Project Management Associate (IPMA)
>>> http://www.jannik-laval.eu
>>> http://rmod.lille.inria.fr
>>> ---
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
My last improvement brake the test testFlowInLayout.
I will try to fix this asap...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I do not have a solution, but this is really annoying. In addition to
the time taken by loading Moose, it makes 10 minutes just to check
what are are dependencies Mondrian has.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
With the great help of Lukas, we installed a Hudson continuous
integration server for Moose. You can find the reports at:
http://hudson.moosetechnology.org
At the moment, there is only one configuration that builds every night
the latest development image by loading the default from the latest
ConfigurationOfMoose, and by running all tests from this Configuration
and from all directly included Configurations.
We have 1316 tests from which 3 fail. The result is here:
http://hudson.moosetechnology.org/job/moose-latest-dev/
A by-product of the build system is that you can always download the
latest nightly build images. For example:
http://hudson.moosetechnology.org/job/moose-latest-dev/26/artifact/
Cheers,
Doru
--
www.tudorgirba.com
"Presenting is storytelling."