Re: TableReport slow down

Le 02/01/2016 09:45, Johan Brichau a écrit :
> My suggestion is not to use the #printOn: method for rendering the
> object on a Seaside canvas, but rather implement a #renderOn: method
> that avoids concatenating the String and WideString instances.
>
Thanks for the tip it helps.
However use of renderOn: will have some large implication on my Seaside
components. Each use case of this object in component need to be
rewritten to use only render:. I don't like much this idea, it makes the
written code less elegant and consistent.

Next, I understand now why I noticed this important slow down from the
Pharo Inspector when browsing such collection object with € symbol on
the EyeTreeInspector. I was first believing the slow down was because of
the Inspector, but it is the same problem, which appear more clearly as
a limitation of Pharo itself. I will resume discussion on the Pharo user
list then.

Thanks

Hilaire

-- 
Dr. Geo
http://drgeo.eu
http://google.com/+DrgeoEu

_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside