Re: [Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-17 Thread Mihai Sucan
Le Sun, 17 May 2009 14:30:16 +0300, Lucian Branescu a écrit: > Does anyone know how gecko 1.9.1's full page zoom interacts with > ? Please be more specific. As far as I know, zooming is applied "transparently" - the Web application does not "observe" the changes. Dimensions of all element

Re: [Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-17 Thread Lucian Branescu
I was thinking whether it has some scaling optimisations, since it does a lot of it with the zoom. 2009/5/17 Mihai Sucan : > Le Sun, 17 May 2009 14:30:16 +0300, Lucian Branescu > a écrit: > >> Does anyone know how gecko 1.9.1's full page zoom interacts with ? > > Please be more specific. > > As f

Re: [Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-17 Thread Lucian Branescu
Does anyone know how gecko 1.9.1's full page zoom interacts with ? 2009/5/16 Albert Cahalan : > Martin Langhoff writes: > >> The short version of it is that canvas (and image rendering in >> general) is hurting lots due to the dpi being hardcoded to 134 >> which forces Gecko into image scaling gam

Re: [Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-15 Thread Albert Cahalan
Martin Langhoff writes: > The short version of it is that canvas (and image rendering in > general) is hurting lots due to the dpi being hardcoded to 134 > which forces Gecko into image scaling games. Just setting > layout.css.dpi to 96 makes Browse much snappier in general, > and incredibly faste

Re: [Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-15 Thread Lucian Branescu
This is very interesting, similar to the problem Qt used to have on Maemo. I was always surprised by report of being slow on the XO, it's probably the fastest and the lowest overhead drawing technology available to JavaScript. 2009/5/15 Martin Langhoff : > On Fri, May 15, 2009 at 9:56 AM, Martin

Re: [Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-15 Thread Martin Langhoff
On Fri, May 15, 2009 at 9:56 AM, Martin Langhoff wrote: > - I am intrigued, hulahop sources say it's hardcoded to 200dpi (and > that jives with our screen) - why does it end up being 134? Should it > be 200dpi? Would that hit the fast paths properly? (Mihai: does 200dpi > make it better?) At leas

[Sugar-devel] Browse.xo performance & resolution - Hulahop 200dpi vs Browse 134dpi

2009-05-15 Thread Martin Langhoff
Hi OLPCistas, Sugaristas, Mihai (GSoC participant on the Moodle side of things) has been experimenting with Browse.xo and the performance of its canvas implementation. Out of the box, it is awfully slow (while other aspects of Browse are fairly optimised). He tells the story here, including perf