-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future strategy for icon management #2960
Comments
|
My
|
did we already consider creating a font at build time from input vector data and use that? Egui already handles font rendering, meaning that a vector graphics library is already dragged in |
We'd end up pulling a font-building library I guess, but I like this idea :) |
Example of putting icons in a font for egui: https://github.com/amPerl/egui-phosphor |
It appears to be just using pre-packaged fonts. Which leads to the idea of storing our icons in a font file, and just editing/adding icon with e.g. FontForge (or some scripts). Then we just need a bunch of constants to map icon names to unicode characters. |
Online tool to build font from SVG: https://www.glyphter.com It should be relatively straightforward to have a script converting a bunch of SVGs into a TTF font and generate the corresponding |
One downside of the font approach is that it will only support monochrome icons (epaint doesn't support color emojis) |
Whatever we chose should be compatible with: |
(forked from discussion in #2920)
We currently use 24x24px png exported from Figma.
This approach has two shortcomings:
Moving forward, our strategy for icons should enable:
cc @martenbjork @emilk
The text was updated successfully, but these errors were encountered: