Pekr, my experiment showed AGG on ARM without FPU was way slower than the native implementation of Android Canvas engine...mainly because the Canvas uses integer based rasterizer etc.
Pekr
well, are there really devices, with no FPU these days?
Cyphre
For example my Smasung Galaxy mini phone :-) AFAIK these low-ends are owned by a lot of people who doesn't have big enough pockets to handle the much bigger, expensive and powerful ones.
Pekr
That might be a history sooner, than R3/View exists for such devices :-)
Cyphre
Yes, but it is always good to have some flexibility and choose which graphics setup is more suitable for your target platform.
Also If you need pixel-precise results in your app you can still use the Agg for making hi-quality output etc.
Pekr
so what's available on Android for e.g.? Skia? Cairo? Or their Canvas engine is another different thing?
Cyphre
AFAIK Android uses Skia for the Canvas graphics.
Pekr
Well, without R3 core being compiled to droid, there's no chance to get R3 running there, no? So your tests involved pure AGG test, with no relation to REBOL?
Cyphre
Yes, but you can guess how Rebol will be fast on such device. The cpu I have has around 600Mhz so just remember when you run Rebol 10 years ago on your desktop ;)
Pekr
will it influence REBOL in overall? I mean - even Core speed? Most probably yes, when flot calculations are done?
hmm, maybe we should move to another group ...
Cyphre
I guess so :)
Kaj
OK, so your engine could use the Enlightenment canvas as a rendering backend. :-) That's pretty much what we're planning for Red: dialects for multiple native backends
Kaj
Today was Syllable's tenth anniversary. I took the opportunity to present the Enlightenment graphics engine that I've been porting in the past months