mirror of
https://github.com/servo/servo.git
synced 2025-06-19 14:48:59 +01:00
ad53e95080
I've done a bit of job to get this done. Right now readback is still used, but we have a `LayerId` -> `CanvasRenderer` map on the paint task, that we can use to get rid of that. I'd want review, to see if this is a good approach (I know it's not the initial `CanvasId` -> renderer approach, but it's pretty similar, since a canvas involves a `PaintLayer`). I had to do a bit of refactoring to avoid cyclic dependencies between canvas and gfx. I'd want you to review them too. It's mergeable and doesn't break any tests :P Some of my main concerns: * Does the canvas render really need to be behind an `Arc<Mutex<T>>`? * I can't clone a `NativeSurface` right now (that's why the `SendNativeSurface()` msg is unimplemented in the WebGL task). It should be easy to add that to rust-layers, supposing the caller is responsible to mark it as non-leaking, any reason to not do it? cc @jdm @pcwalton <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6083) <!-- Reviewable:end --> |
||
|---|---|---|
| .. | ||
| Cargo.toml | ||
| compositor.rs | ||
| compositor_layer.rs | ||
| compositor_task.rs | ||
| constellation.rs | ||
| headless.rs | ||
| lib.rs | ||
| pipeline.rs | ||
| scrolling.md | ||
| scrolling.rs | ||
| windowing.rs | ||
