Confirmed users
166
edits
SMIL:Timing Model: Difference between revisions
m
→nsISMILTimeContainer: -- fixed typo in Schmitz
m (→nsSMILInterval) |
m (→nsISMILTimeContainer: -- fixed typo in Schmitz) |
||
| Line 17: | Line 17: | ||
== nsISMILTimeContainer == | == nsISMILTimeContainer == | ||
This is a SMIL time container as described in [http://www.w3.org/TR/2005/REC-SMIL2-20050107/ SMIL 2.0]. I'm not pretending to understand or even to have read the SMIL 2.0 spec, but | This is a SMIL time container as described in [http://www.w3.org/TR/2005/REC-SMIL2-20050107/ SMIL 2.0]. I'm not pretending to understand or even to have read the SMIL 2.0 spec, but Schmitz describes a similar class so I think this interface would allow us to later support SMIL 2.0 time containers (not required by SVG). | ||
The <tt>getNextChange()</tt> method is something to be suspicious of. This seems like an obvious optimisation to me. If, for example, a document doesn't contain any animations, they are all inactive or the document fragment is paused then it should be possible to inform the animation controller of this so it can suspend the animation timer. Likewise, if no changes are likely to occur, and no events need to be generated for another 60 seconds, it should be possible to suspend the timer. | The <tt>getNextChange()</tt> method is something to be suspicious of. This seems like an obvious optimisation to me. If, for example, a document doesn't contain any animations, they are all inactive or the document fragment is paused then it should be possible to inform the animation controller of this so it can suspend the animation timer. Likewise, if no changes are likely to occur, and no events need to be generated for another 60 seconds, it should be possible to suspend the timer. | ||