Move `Debugger` and `Windowed` to a better location

We move `renderer::Debugger` to `layout::Debugger` and
`renderer::Windowed` to `window::Renderer`.

1 files changed, 0 insertions, 26 deletions

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<Message>(
-        &mut self,
-        defaults: &Self::Defaults,
-        widget: &dyn Widget<Message, Self>,
-        layout: Layout<'_>,
-        cursor_position: Point,
-        color: Color,
-    ) -> Self::Output;
-}