Thanks for your analysis.
Should we open a enhancement issue for UFFI?
Stf
On Thu, Apr 5, 2018 at 4:09 PM, Henrik Sperre Johansen
wrote:
> HilaireFernandes wrote
>> After some more investigation, I think it is not the greated bottleneck.
>>
>> When I render points not as discs but as Square, Ath
Le 05/04/2018 à 16:09, Henrik Sperre Johansen a écrit :
DRGEO:
20.9% {27116ms} DrGPointMorph>>drawOnAthensCanvas:
|16.7% {21720ms} AthensCairoCanvas(AthensCanvas)>>createPath:
Storing the path in DrGPointMorph, rather than recreating for each draw:,
should save alot of time.
Indeed sh
On Thu, Apr 5, 2018, 16:09 Henrik Sperre Johansen <
henrik.s.johan...@veloxit.no> wrote:
> HilaireFernandes wrote
> > After some more investigation, I think it is not the greated bottleneck.
> >
> > When I render points not as discs but as Square, Athens is happy. I
> > guess the Cairo way of doin
HilaireFernandes wrote
> After some more investigation, I think it is not the greated bottleneck.
>
> When I render points not as discs but as Square, Athens is happy. I
> guess the Cairo way of doing this is very slow because its seems Cairo
> does not come with dedicated disc rendering code, i
if I remember correctly that Cairo does not support arc and that igor
was doing point interpolation to support it.
stef
On Thu, Apr 5, 2018 at 11:33 AM, Hilaire wrote:
> After some more investigation, I think it is not the greated bottleneck.
>
> When I render points not as discs but as Square,
After some more investigation, I think it is not the greated bottleneck.
When I render points not as discs but as Square, Athens is happy. I
guess the Cairo way of doing this is very slow because its seems Cairo
does not come with dedicated disc rendering code, it must be render with
portion o
Looking at the profile, Athens spend time on some of my widgets:
1. LabelMorph with a workaround in the draw method as:
drawOnAthensCanvas: aCanvas
"Work around for the conflicting size font problem"
aCanvas pathTransform restoreAfter: [
aCanvas pathTransform scaleBy: 1.1.
"d
You mean one iteration?
Hilaire
Le 04/04/2018 à 20:05, Thierry Goubier a écrit :
Can you profile a refresh / a redraw?
We've seen many times Morphic being qualified as slow, and the culprit
were very badly programmed widgets.
Thierry
--
Dr. Geo
http://drgeo.eu
Le 04/04/2018 à 19:31, Hilaire a écrit :
It is already animated :)
https://twitter.com/GNUDrGeo/status/981583820037160961
But canvas get slow when I push to 500 montecarlo iterations, for example.
Can you profile a refresh / a redraw?
We've seen many times Morphic being qualified as slow, an
It is already animated :)
https://twitter.com/GNUDrGeo/status/981583820037160961
But canvas get slow when I push to 500 montecarlo iterations, for example.
Le 04/04/2018 à 19:03, Stephane Ducasse a écrit :
Hilaire
do you want to see an animation?
Stef
--
Dr. Geo
http://drgeo.eu
Hilaire
do you want to see an animation?
Stef
On Wed, Apr 4, 2018 at 3:49 PM, Hilaire wrote:
> Hi,
>
> I discover this Dr. Geo Smalltalk sketch to animate is about 60% slowler on
> P7 compare to P3:
>
> | fig point comment x y random inArc tries|
> "Monte-Carlo PI approximation"
> fig := DrGeoC
Clement
if it would be nice to have the fastCorner and friends added to rectangle.
On Wed, Apr 4, 2018 at 5:33 PM, Clément Bera wrote:
> Hi Hilaire,
>
> Do you have to use the world or Morphic at all ?
>
> I wrote 2 different real-time 2D games at 50fps in Pharo [1,2]. I tried
> using Morphic bu
Hi Clement,
I know about your SDL games demo. But DrGeo is really Morphic based, so
yes it is mandatory. I suspect there is may be something going on
between Cairo/Athens/Morph. For regular mouse use of DrGeo it is just
fine. It is when pusing to the limite with Smalltalk sketch and
animating
Hi Hilaire,
Do you have to use the world or Morphic at all ?
I wrote 2 different real-time 2D games at 50fps in Pharo [1,2]. I tried
using Morphic but that was crazy slow I could not even get 20fps. Instead I
use direct bindings to Cairo surface and SDL2 window and I don't open the
world morph at
14 matches
Mail list logo