18 Jun
2010
18 Jun
'10
11:53 a.m.
Hi Jannik,
I tried a DSM. The eDSM gives me a subscript out of bounds error
somewhere deep in the contentOfCell: aView for: aCell with: aPackage
out: aBoolean method.
I applied this on the namespaces of JUnit. I attached the debug log.
Cheers,
Doru
On 18 Jun 2010, at 07:19, Laval Jannik wrote:
Hi,
Doru, do you do a DSM or a eDSM ?
With a eDSM, I do not see difference, I think there are some
computation somewhere else.
Alex, do you cache all things ?
Thanks,
Jannik
On Jun 17, 2010, at 17:47 , Tudor Girba wrote:
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
I tested on a regular DSM with 259 namespaces and
I can now
properly scroll once it gets displayed.
Jannik, Veronica, could you check in your cases?
Cheers,
Doru
On 17 Jun 2010, at 16:30, Tudor Girba wrote:
---
Jannik Laval
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Alex,
--
www.tudorgirba.com
"Some battles are better lost than fought."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev > Indeed, this caching should happen for all
properties and for
> all shapes (both for nodes and for edges). I think that Alex
> stopped in the middle because he did not know whether this
> caching had an effect or not.
I was wondering whether it would make sense to do this for all
the metrics. Apparently yes, I then continued. All shape
parameters should be cached.
> Alex, could you take a look at that?
Done. Mondrian-Alexandre_Bergel.470
Great. I checked a bit the implementation, and I would only
suggest to check for isCached in the attributeAt:ifAbsent: method,
instead of in every *For: methods.
> The next question is that if the border color
is called all the
> time, what is the use of the bitmap cache?
The bitmap is for not having to display inner nodes. Recursion
takes times.
I know, but if you compute it once why do you still need to re-
render?
Cheers,
Doru
>> ======
>> |view o |
>> view := MOViewRenderer new.
>> o := OrderedCollection new: 100.
>> 1 to: 100 do:[:i | o add: i].
>> (view shape: (MORectangleShape new
>> width: [:e | 200];
>> height: 200;
>> withBorder;
>> borderColor: [:e | (Delay forMilliseconds: 50) wait. Color
>> gray])).
>> view nodes: o.
>> view layout: (MOGridLayout new gapSize: 1).
>> view open
>> ======
A better version could be
-=-=-=-=-=-=-=-=-=-=-=-=
|view o a |
a := {0}.
view := MOViewRenderer new.
o := OrderedCollection new: 100.
1 to: 100 do:[:i | o add: i].
(view shape: (MORectangleShape new
width: [:e | 200];
height: 200;
withBorder;
borderColor: [:e | a at: 1 put: (a first + 1). Color gray])).
view nodes: o.
view layout: (MOGridLayout new gapSize: 1).
view open.
a
-=-=-=-=-=-=-=-=-=-=-=-=
Just inspect the expression, and see if the array a changes over
the time.
Is there any remaining problem left in Mondrian related to the
speed issue?
Cheers,
Alexandre
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Some battles are better lost than fought."