#16101 closed enhancement (fixed)
Allow using non-system fonts from files with BFont
Reported by: | calvinb | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta5 |
Component: | Kits/Interface Kit | Version: | R1/Development |
Keywords: | bfont | Cc: | |
Blocked By: | Blocking: | #13361 | |
Platform: | All |
Description (last modified by )
BFont can only work with fonts installed into the system (packaged/non-packaged). It would be nice to be able to load external fonts from the filesystem.
Use case: private fonts for applications/games not relevant to the rest of the system, applications like font previewers/installers, web browsers with @font-face.
Change History (8)
comment:1 by , 5 years ago
Blocking: | 13361 added |
---|
comment:2 by , 5 years ago
Description: | modified (diff) |
---|
comment:4 by , 2 years ago
Milestone: | Unscheduled → R1/beta5 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Patch merged in hrev56649. It seems it was not included in beta4, should we do that or is it too risky?
comment:5 by , 2 years ago
Too risky for now. Let's hold off and merge it later, after it's been well-tested.
comment:6 by , 2 years ago
How about just the interface in BFont (and maybe ServerProtocol) with the implementation returning an error?
comment:7 by , 2 years ago
I'm not sure what the benefit of adding just the interface would be.
The risky part, in my opinion, isn't the new font loading, but rather the fact that the global font manager was refactored. If the new font loading is broken it's not a big deal, but if the core font handling turns out to be broken that would be a real shame for beta4.
comment:8 by , 2 years ago
Adding just the interface will allow building the new haikuwebkit releases with beta4 buildbots, even if they can't display custom fonts on beta4. So I can continue making regular haikuwebkit releases
I posted a review patch to Gerrit: https://review.haiku-os.org/c/haiku/+/4790
I'm not positive this is the correct approach, and welcome all comments and criticisms!!
it's barely tested but I wanted to make sure I wasn't heading the wrong direction.