Skip to content

Conversation

@VladiStep
Copy link
Member

Description

When there was the "ExportFontData.csx" script, there was a window that allowed you to select only few fonts for exporting.
This PR reimplements the selection window, but it's WPF instead of WinForms.
image

Notes

@C-arth asked me to make this, so thanks to him.

@github-actions
Copy link

@CST1229
Copy link
Contributor

CST1229 commented Jun 26, 2025

wouldn't this make the script not cross-platform again? (which is the whole reason that functionality was removed from it)

@VladiStep
Copy link
Member Author

VladiStep commented Jun 26, 2025

Oh, hm, fair point.
But for now, it can stay like that? It's not difficult to revert the changes when UTMT will become cross-platform

@VladiStep
Copy link
Member Author

VladiStep commented Jun 26, 2025

Also, WPF can be ported to Avalonia much easier than WinForms?
And it's also compatible with the dark mode now.

@CST1229
Copy link
Contributor

CST1229 commented Jun 26, 2025

Also, WPF can be ported to Avalonia much easier than WinForms? And it's also compatible with the dark mode now.

what about the CLI?

(i think one way here would be to make this a separate GUI-only script, maybe like ExportSpecificFonts.csx, and keep the current ExportAllFonts that works everywhere. there already are a few scripts that rely on GUI and don't work on the CLI, so this isn't exactly a new thing)

@colinator27
Copy link
Member

Yeah, I'm not sure I like the idea of having GUI-specific scripts like this anymore, unless the GUI part of it is part of the scripting interface.

@colinator27 colinator27 added the new script Tag for PRs with new scripts that we might consider adding to awesome-utmt label Jan 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new script Tag for PRs with new scripts that we might consider adding to awesome-utmt

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants