| || |
Re: Video Tour of My Verizon Galaxy Nexus
No I read the whole post, that's why I prefaced my statement with IIRC. I do remember, as others have said, that they mentioned having to rewrite all of Android's code in order for it to operate like iOS or WP7, and to me that sounded like it was a core part of the way Android always operated. I could be wrong tho. I mean, that's certainly how the browser on my Evo 3d and 4g have worked. I'll go reread that post.
Originally Posted by MowDownJoe
EDIT: I reread the post, and the new one, and unfortunately she removed the part that I was referencing (about iOS prioritizing touch inputs above everything else). However, you're totally right that they changed the way the browser renders pages to be more like iOS in Honeycomb. Here's the quote:
• When people have historically compared web browser scrolling between Android and iOS, most of the differences they are seeing are not due to hardware accelerated drawing. Originally Android went a different route for its web page rendering and made different compromises: the web page is turned in to a display list, which is continually rendered to the screen, instead of using tiles. This has the benefit that scrolling and zooming never have artifacts of tiles that haven’t yet been drawn. Its downside is that as the graphics on the web page get more complicated to draw the frame rate goes down. As of Android 3.0, the browser now uses tiles, so it can maintain a consistent frame rate as you scroll or zoom, with the negative of having artifacts when newly needed tiles can’t be rendered quickly enough.
Ok I'll stop hijacking this thread now.