I wrote the initial page with help from various teams. We should avoid having 2 pages that are very similar unless we plan on having them diverge. Whats the target audience for [2]? for [1] I'm assuming that the user can already perform custom builds of gecko which is required to dig into the display list/layers dump to analyze/report certain problems. If we assume that the audience in [2] can't make custom builds and dig into the platform then to better fit the audience some of these steps should be removed and replaced with instructions on using the upcoming devtools Timeline. Actually this page predates the timeline so both versions should suggest checking against the Timeline under the relevant sections.
On Wed, Oct 8, 2014 at 10:36 AM, Chris Mills <[email protected]> wrote: > Hi all, > > I’ve taken the rather excellent App performance validation page[1] from > MozWiki, edited it, neatened it up, and published it on MDN[2]. Can someone > who knows about this stuff give the page a proof read for me to make sure > I’ve not got anything wrong? > > Thanks. > > [1] https://wiki.mozilla.org/FirefoxOS/Performance/App_Performance_Validation > [2] > https://developer.mozilla.org/en-US/Apps/Build/Performance/App_performance_validation > > Chris Mills > Senior tech writer || Mozilla > developer.mozilla.org || MDN > [email protected] || @chrisdavidmills > > > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
