On 2026-06-22 19:31, Dan Williams wrote:
I think Michael explained to me that we’d eventually like to use the Qt font code, but there are still some rough spots. Pretty sure we wouldn’t want to use any of the freetype code for macOS if we can help it here.
Not necessarily. I don't know which of thepotential rendering paths would be best in the long run; that might be worth some further investigation at some point.
For now, the one using Cairo is certainly the most mature for the qt6 vcl plugin (and at least for Linux, I don't see any urgent need to switch away from it), and there's an experimental QFont-based one. Investigating whether introducing a new one using Skia as another alternative might be yet another potential alternative that might be worth exploring at some point in the future.
This made me start poking at welding for the OS X plugin. I don’t have code yet, just trying to see if we can programmatically create all the widgets we might need first. Any reason you can think of that welding wouldn’t work for vcl/osx?
Do you mean creating native widgets using the native macOS widget toolkit instead of using Qt?
If so: As long as the macOS API is reasonably similar to the weld API (current or with any necessary adjustments to the weld API to support another toolkit), I don't see any reason why it shouldn't be possible.
From an implementation/maintenance perspective, each additional weld implementation is extra work (and harder to deal with for most developers if it requires macOS), but if that's superior to Qt in your opinion, I'd say it's certainly worth considering that option as well.
OpenPGP_signature.asc
Description: OpenPGP digital signature
