For an ui element made out of graphics::Canvas, is it better to

1. build a new ui::Canvas

2. make it so that ui::Image can accept either graphics::Image or graphics::Canvas

3. make it so that there's a Drawable trait that has fn draw<Q: IntoQuad>(&self, quad: Q, target: &mut Target), so that ui::Image accepts a &dyn Drawable trait object.

1 is the most logical given t

Describe the current state of the problem
Currently, there is a text input for a font family, similar to what works for CSS font-family property. This is good for users who work with CSS, but it is not intuitive for those who don't.

Describe the solution you'd like

• A help icon that will show some examples of proper font families, and the rules for writing them;
• A font picker fo

It would be nice to have a component that can expose the frames of an animated GIF image using the Animation interface; I'm picturing something like this:

import { useType, useNewComponent, GIF, useDraw } from "@hex-engine/2d";
import someGifFile from "./whatever.gif";

function MyComponent() {
  useType(MyComponent);

  const gif = u

ÖbEngine already provides three const variables : VERSION_MAJOR, VERSION_MINOR and VERSION_PATCH.
It would be nice to encapsulate version into an object which support comparison, equality (with object or string)