On Wed, Jun 10, 2009 at 11:37 AM, Luke Kenneth Casson Leighton < [email protected]> wrote:
> (...) > once done, you'd be able to pretty much drop the exact same olpc > browser onto KHTML, webkit or xul. and, other than the c++ > rtti-related bugs in KHTML, you'd get exactly the same functionality. Cool. Things are getting better indeed. Two things to consider when looking at this... - Startup, memory use and general responsiveness on XO hardware and general netbook hw. The current Browse.xo compares _very_ favourably with Firefox and Opera on XO-1 hardware. - Behaviour in non-standard-dpi screens the require scaling. The XO screens have 200dpi physical pixels, with a 'perceived dpi' of ~133px. Currently gecko suffers a lot due to how images end up being scaled -- see the discussion in http://wiki.laptop.org/go/HTML_canvas_performance -- and this is bound to affect other hardware as well. cheers, m -- [email protected] [email protected] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff
_______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
