"Wu, Yong" <[email protected]> writes: > Solutions: > We introduced the native rendering mode to Fennec.
I am not sure but someone has been working on this and has a patch, which you might want to check: https://bugzilla.mozilla.org/show_bug.cgi?id=528551 http://dougt.org/wordpress/2009/11/fast-flash-fennec/ >Basically the native rendering is to draw directly to X window as what Firefox >do. It is pointed to avoid the tile manager conditionally. We will let both >mode (native rendering & tile rendering) co-exist for Fennec. > 1, By default browser will enter tile rendering mode. Each tab can either be > native rendering or tile rendering mode. At every time, browser can show only > one tab content thus browser will enter native rendering when the selected > tab is under native rendering. > 2, We provided mechanism to switch between tile rendering and native > rendering. Such transition is basically free: It does not change the page > layout. There is no need to trigger any repaint events from the rendering > engine. It does not change the user status (loggined, text inputing, etc..). > 3, We have limited support for panning In native rendering mode. We enabled > panning to access the tabs/history/preference bars. But, to view web content, > user need to use the scrollbars, or page built-in mechanism, like Firefox. > This is to fix the Google maps and text area inputting issues. > 4, Plugins are supported in a better way. Firstly, Java/PDF plugins will be > supported. Secondly, we can have the best flash play performance without > changing the flash plugin code. And finally, it is OOPP friendly. > 5, We enter the native rendering in the following four scenarios: a) > automatically enter native rendering for any full-screen objects, for > instance PDF or full screen video display. b) automatically enter native > rendering when the dominant viewport of user content view is a plugin window, > esp, user are watching a flash video. c) suggest to enter native rendering > mode when there is embedded Java/flash plugins. This will enable Java plugins > and improve flash performance. d) at any time, user could choose to > enter/leave native rendering manually (via a toolbar button). > > > Main concerns: > 1, In native rendering mode, the panning/scrolling experience is different > from the tile rendering. And considering the scrolling performance, it is > slower than in tile rendering - due do the continuous reflowing/redrawing. In > the tile rendering mode, it simply avoids the redrawing by the tiled cache. > 2, To the end user, the native rendering concept, and suggestion for users to > enter a native rendering mode can be confusing. > > Any comments? Please! > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > -- Roger WANG _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
