Doru
when I try to run the test in Moose-All in Squeak I get a DNU model
allMethods....
I want to check in VW but I do not succeed to run the tests. I should
be sooooo fucking stupid.
What a huge improvement this UI terribly excellent. I lost 20 min and
now I'm pissed off.
allMethods does not seem to be implemented on mooseModel or I'm blind.
But again I may be totally stupid.... I start to love really squeak.
I put a halt in the setUp method of the CandidateListOperator which is
inoved in the ressources setup
Now I
setUp
self halt.
groups := (model allMethods reject: #isAbstract) groupedBy: #signature
Hi all
I loaded the
- latest version of FAME
- mse-lr
- OB
- moose-all
Now when I load moose-all I get a
"FMBookMock You must resolve these dependencies before you will be
able to load these definitions: FMBookMock>>mooseButtons
FMBookMock>>viewer"
:(
Stef
Hi,
I just explored moose utilities on moose website and I found that
Package DNA had been modified?!!
I found he last version of Package blueprints (I modified this version
from more than 2 months), and I did not find Package fingerprint?
Is it the same problem that happened with Java4Moose?
thanks,
hani
hi!
Last time I checked the moose.unibe.ch website, I was surprised to see
that the Java4Moose section has disappeared from the Tools section.
This has the a smell of old backup restoration. Someone may give an
update on this?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi
I really enjoyed the dojo.
Now how can we proceed? I would really like to have a Moose up and
running in Pharo.
Doru do you have an idea when you will have time to work on FAMIX 30?
From my side I will work on the extractor and populate FAMIX-
Implementation and Famix-Smalltalk.
Stef
Dear list,
today I installed Moose, and, on top of that, ClusterFinder, which
would simply refuse to work - sometimes it will choke on a "Subscript
out of bounds" immediately, sometimes it will show a growing progress
bar and then complain about the message #writeStream not being
understood (while, at the same time, "errorr!a CodeFoo.Deprecation"
messages appear).
I installed the most recent versions of Moose and ClusterFinder. What
do I have to do to make this work?
Best,
Michael
Hi Azadeh,
First, you have to create nodes to be able to draw edges.
Second, in your case, I guess the simplest thing is to use the numbers
as the models for the edges and just specify "from:" from the first
collection and "to:" from the second collection.
Perhaps something like this would work:
viewFrom: col1 to: col2
| view |
view := Mondrian.ViewRenderer new.
view node: col1 forIt: [
view nodes: col1.
view verticalLineLayout.].
view node: col2 forIt: [
view nodes: col2.
view verticalLineLayout.].
"we just created 2 nodes for the two collections and inside we added a
node for each element"
"we also laid out the nodes vertically inside each root node"
view edges: (1 to: col1 size) from: [:index | col1 at: index] to:
[:index | col2 at: index].
view open
Cheers,
Doru
On Jun 3, 2008, at 7:09 PM, azadeh wrote:
> Hi,
> I have a question about Mondrian .
> I want to visualize an exttraction result by ViewRenderer .
> As the result I have two OrderedCollections that have a semantic
> relation between their entities.
> Now i need to make edges from col1 index:1 to col2 index:1; col1
> index:2 to col2 index:2; in this way.
> I tried this way:
> viewfrom : col1 to:col2
> view := Smalltalk.Mondrian.ViewRenderer new.
> i := 1 .[i < (col1 size)] whileTrue:[ view1 edges: col1 from:
> [ col1 at: i] to:[col2 at:i]. i := i + 1.] .
> view open.
> or this way:
> view1 edges: col1 fromAll: [:model| col1] toAll:[:model| col2].
> ps1: the edges are from col1 to col2.
>
> What should i do please?
>
> Best,
> Azadeh
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Every successful trip needs a suitable vehicle."
Hi Dominique,
I saw that you added an extension to Collection. I like the change,
but I need to say two things:
- please use just camel case in the names of the methods (no _)
- actually, I would say that the fix would be better in the groupedBy:
method. What do you say?
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"When people care, great things can happen."
