from .color import Color
import pygame
# TODO: fix this with a dynamic load
from .draw_engine import DrawEngine


class PygameDrawEngine(DrawEngine):
    def init(self):
        self.screen = pygame.display.set_mode((world.WIDTH, world.HEIGHT))
        self.buffer = pygame.Surface((world.WIDTH, world.HEIGHT), pygame.SRCALPHA)

    def render(self, background_color: Color, drawables: list["Doodle"]):
        self.buffer.fill((*background_color, 255))
        for d in sorted(drawables, key=lambda d: d._z_index):
            d.draw()
        self.screen.blit(self.buffer, (0, 0))
        pygame.display.flip()

    def circle_draw(self, c: "Circle"):
        pygame.draw.circle(self.buffer, c.rgba, c.world_vec, c.radius_val)

    def rect_draw(self, r: "Rectangle"):
        # TODO: make accessors
        rect = pygame.Rect(
            r.world_x - r._width / 2,
            r.world_y - r._height / 2,
            r._width,
            r._height,
        )
        pygame.draw.rect(self.buffer, r.rgba, rect)

    def line_draw(self, ll: "Line"):
        pygame.draw.aaline(self.buffer, ll.rgba, ll.world_vec, ll.end_vec)


class World:
    """
    This class is a singleton, only one instance should ever exist.

    A common reason for this is a class that manages a resource of some kind,
    in this case, our screen.
    This class needs to track where entities are in relation to the screen,
    and will hold a reference to a pygame variable that lets it draw to the screen.

    Multiple instances of this class would

    There are two schools of thought about this pattern:

    You can use this pattern as we do here, with no extra code.
    We instead define an instance variable "world" below, and
    documentation would show users to use that global variable.
    It would technically be possible for someone to instantiate
    a "world2 = World()" instance, but doing so would be admonished
    in documentation and not supported.

    You could optionally denote this by naming the class _World.

    Others prefer to have code-level enforcement of this policy.
    There's a nearly infinite number of ways to do this, including
    simply keeping a global "_instance_created" variable that gets
    set to a non-None value after first creation, and then
    raises an exception on invalid use, or with a bit of cleverness
    returns the single-instance no matter how hard the user
    tries to create a new one.
    """

    WIDTH = 800
    HEIGHT = 600
    FPS = 60
    MS_PER_FRAME = 1000 / FPS

    _instance = None

    def __init__(self):
        # This logic forms the basis of a check for prior instances.
        # Code could be added here to explicitly disallow them.
        if self._instance is None:
            self._instance = self
        self._drawables = []
        self.background_color = Color.WHITE
        self.screen = None
        self.draw_engine = PygameDrawEngine()

    def init(self):
        """
        Delayed initialization, can't be run at start
        but must be run once.
        """
        if self.screen:
            raise ValueError("Can't initialize world twice!")
        pygame.init()
        self.clock = pygame.time.Clock()
        self._elapsed = 0
        self.draw_engine.init()

    def clear(self):
        self._drawables = []

    def add(self, drawable):
        self._drawables.append(drawable)

    def tick(self):
        for d in self._drawables:
            d.update()

    def update(self):
        """
        Update & draw world to screen.
        """
        # update
        self._elapsed += self.clock.tick(self.FPS)
        while self._elapsed > self.MS_PER_FRAME:
            self._elapsed -= self.MS_PER_FRAME
            self.tick()

        # rendering
        self.draw_engine.render(self.background_color, self._drawables)



# our singleton instance
world = World()