From e45497dfd6d401d8da74a8167b876a20690ddcac Mon Sep 17 00:00:00 2001 From: Héctor Ramón Jiménez Date: Fri, 10 Jan 2020 01:58:55 +0100 Subject: Move `Debugger` and `Windowed` to a better location We move `renderer::Debugger` to `layout::Debugger` and `renderer::Windowed` to `window::Renderer`. --- native/src/renderer/debugger.rs | 26 -------------------------- 1 file changed, 26 deletions(-) delete mode 100644 native/src/renderer/debugger.rs (limited to 'native/src/renderer/debugger.rs') diff --git a/native/src/renderer/debugger.rs b/native/src/renderer/debugger.rs deleted file mode 100644 index 30f3d9a0..00000000 --- a/native/src/renderer/debugger.rs +++ /dev/null @@ -1,26 +0,0 @@ -use crate::{Color, Layout, Point, Widget}; - -/// A renderer able to graphically explain a [`Layout`]. -/// -/// [`Layout`]: ../struct.Layout.html -pub trait Debugger: super::Renderer { - /// Explains the [`Layout`] of an [`Element`] for debugging purposes. - /// - /// This will be called when [`Element::explain`] has been used. It should - /// _explain_ the given [`Layout`] graphically. - /// - /// A common approach consists in recursively rendering the bounds of the - /// [`Layout`] and its children. - /// - /// [`Layout`]: struct.Layout.html - /// [`Element`]: struct.Element.html - /// [`Element::explain`]: struct.Element.html#method.explain - fn explain( - &mut self, - defaults: &Self::Defaults, - widget: &dyn Widget, - layout: Layout<'_>, - cursor_position: Point, - color: Color, - ) -> Self::Output; -} -- cgit