Oh yes, you're right. That said, of course, "smoothness" is something all app developers should be shooting for, so it might be worth adding a whole new section just with tips on how to be smooth.
On Mon, Jan 26, 2015 at 5:24 PM, Milan Sreckovic <[email protected]> wrote: > Valid point, and something we should be doing, but just to be sure - Silk > is about “smoothness”, rather than “performance”. In other words, the > claim is that, say, 50 well placed frames are better than 60 poorly spaced > frames. You may have heard the term “frame uniformity” being bounced > around, and a bunch of others, but Silk as such should not be expected to > increase the number of frames that you see. You’ll just enjoy the ones you > do see more :) > — > - Milan > > > > On Jan 26, 2015, at 17:15 , Eric Shepherd (Sheppy) <[email protected]> > wrote: > > Also, if you (or anyone) have any tips for maximizing graphics performance > in Firefox OS apps, please let me know. I'd like to keep collecting these > to put on MDN. > > In particular, these pages should have any ideas you have added to them as > appropriate (you can do it, or you can send ideas to me or to Chris Mills > and we'll handle it for you); > > > https://developer.mozilla.org/en-US/Apps/Build/Performance/App_performance_validation > > https://developer.mozilla.org/en-US/Apps/Build/Performance/Performance_fundamentals > > Or actually to any of the pages under > https://developer.mozilla.org/en-US/Apps/Build/Performance > > On Mon, Jan 26, 2015 at 2:06 PM, Mason Chang <[email protected]> wrote: > >> Hi all, >> >> Silk, which is a project to improve smoothness across Firefox OS has >> started to land. There are three parts to it, which you can read more about >> here (http://www.masonchang.com/blog/2015/1/22/project-silk). Today, I >> just enabled the vsync compositor which should create smoother animations, >> which includes scrolling. However, it is quite a big change and we expect >> some problems. If you find any bugs, please file them as a dependent of bug >> 1118530 (https://bugzilla.mozilla.org/show_bug.cgi?id=1118530). You can >> always test the bug by disabling these two prefs: >> >> gfx.vsync.hw-vsync.enabled >> gfx.vsync.compositor >> >> Note: You need a kit-kat based device. I’ve tested on a flame with v180 >> base image and above. Any base image below v180 or non kit-kat based >> devices have known issues. >> >> Thanks, >> Mason >> >> _______________________________________________ >> dev-gaia mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-gaia >> >> > > > -- > > Eric Shepherd > Sr. Technical Writer > Mozilla > Blog: http://www.bitstampede.com/ > Twitter: http://twitter.com/sheppy > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > > > -- Eric Shepherd Sr. Technical Writer Mozilla Blog: http://www.bitstampede.com/ Twitter: http://twitter.com/sheppy
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
