Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1468)

Unified Diff: mojo/services/gfx/composition/interfaces/scheduling.mojom

Issue 1997513002: Mozart: Generalize frame scheduling. (Closed) Base URL: git@github.com:domokit/mojo.git@moz-jank2
Patch Set: add comments Created 4 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « mojo/services/gfx/composition/interfaces/scenes.mojom ('k') | mojo/tools/data/apptests » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: mojo/services/gfx/composition/interfaces/scheduling.mojom
diff --git a/mojo/services/gfx/composition/interfaces/scheduling.mojom b/mojo/services/gfx/composition/interfaces/scheduling.mojom
index 7b5dee1c4d28bc3b79513b9f271f2ee6a5fe86fd..91b09ae61a67c450dbd686b9bcc785f24711793e 100644
--- a/mojo/services/gfx/composition/interfaces/scheduling.mojom
+++ b/mojo/services/gfx/composition/interfaces/scheduling.mojom
@@ -5,26 +5,25 @@
[DartPackage="mojo_services"]
module mojo.gfx.composition;
-// Provides support for scheduling drawing and composition operations
-// for a particular scene.
+// Provides support for scheduling drawing and composition operations.
//
-// Instances of this interface must be obtained from a |Scene|. This interface
-// is modeled separately so as to allow applications to use different threads
-// for scheduling work as opposed to publishing scene updates.
-interface SceneScheduler {
+// Instances of this interface must be obtained from a |Scene| or |Renderer|.
+interface FrameScheduler {
// Asks the compositor to invoke the callback when it is a good time to
// draw the next frame.
//
// The rate at which the callback is invoked may depend on how the scene
// has been embedded. The scene will only receive frame callbacks while
// it is attached to a scene graph which the compositor has been asked
- // to renderer since timing information ultimately derives from the
+ // to render since timing information ultimately derives from the
// renderer. If the same scene is being rendered to multiple destinations
- // with different timing requirements, the compositor will perform rate
- // adaptation as required behind the scenes.
+ // with different timing requirements, the compositor will couple the
+ // scene scheduling to one of the renderers.
//
// The returned |frame_info| provides information about the frame to
- // be drawn.
+ // be drawn. This information should be passed to a
+ // |mojo::gfx::composition::FrameTracker| to apply compensation for
+ // skipped frames before using it.
//
// TODO(jeffbrown): Consider whether we should have the callback be invoked
// immediately rather than on schedule, letting the client set its own
« no previous file with comments | « mojo/services/gfx/composition/interfaces/scenes.mojom ('k') | mojo/tools/data/apptests » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698