0656a2b904
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 Source-Repo: https://github.com/servo/servo Source-Revision: ad53e95080144485e74cd9b9d48ce75e20de4e36
25 lines
592 B
Rust
25 lines
592 B
Rust
/* This Source Code Form is subject to the terms of the Mozilla Public
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
|
|
|
#![feature(core)]
|
|
#![feature(collections)]
|
|
#![feature(rustc_private)]
|
|
|
|
extern crate canvas_traits;
|
|
extern crate azure;
|
|
extern crate cssparser;
|
|
extern crate geom;
|
|
extern crate gfx_traits;
|
|
extern crate util;
|
|
extern crate gleam;
|
|
extern crate num;
|
|
extern crate layers;
|
|
extern crate offscreen_gl_context;
|
|
|
|
#[macro_use]
|
|
extern crate log;
|
|
|
|
pub mod canvas_paint_task;
|
|
pub mod webgl_paint_task;
|