Confirmed users
166
edits
Platform/GFX/Moz2D: Difference between revisions
Jump to navigation
Jump to search
→Testing Moz2D: Player2D
| Line 179: | Line 179: | ||
# Run player2d | # Run player2d | ||
=== | === Recording and playback === | ||
In order to test different backends and conduct performance analysis it is possible to make a recording of calls to the Moz2D API—for example, those used when rendering a certain Web page—and then replay them step by step on different backends. | |||
==== Making a recording ==== | |||
<span style="background:yellow">TBD (following is note-form only)</span> | |||
On a platform where Moz2D content is enabled in Firefox (currently only Windows): | |||
* Create a profile for recording if you don't already have a suitable one,<br><code>c:\Program Files (x86)\Nightly\firefox.exe -no-remote -ProfileManager</code> | |||
* <code>c:\Program Files (x86)\Nightly\firefox.exe -no-remote -P recording -recording http://www.website.com/ -recording-output mytest.aer</code> | |||
Sometimes recordings are prematurely ended and come up empty. This is a known bug and should be fixed soon. | |||
==== Playing a recording ==== | |||
Having made a recording it is possible to replay the steps on different backends using the Player2D tool (see [[#Building Moz2D]] above). The steps can be played back one by one and it is also possible to step backwards and forwards to inspect the result of each step. | |||
The result is as follows: | |||
<span style="background:yellow">Screenshot yet to come</span> | |||
===== Tools available ===== | |||
<span style="background:yellow">Details of analyzing timing, using recordbench etc.</span> | |||
=== Implementing a new backend === | === Implementing a new backend === | ||