Nickez/bb02 lvgl font#1973
Closed
NickeZ wants to merge 6 commits into
Closed
Conversation
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
5 times, most recently
from
eab5042 to
14012c5
Compare
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
from
c2699d6 to
637e61b
Compare
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
3 times, most recently
from
2c5be2d to
0a206bb
Compare
Add a local ttf2lvgl converter that emits the LVGL fmt_txt font subset used by the BB02 OLED UI. Document the new workflow and remove the old ttf2ugui submodule now that generated fonts no longer use the uGUI format.
Check in the generated Arial, Monogram, and password font data in LVGL fmt_txt form. Add the local LVGL include shim used by these generated font sources.
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
from
0a206bb to
8059edb
Compare
Switch the BB02 OLED UI from the old uGUI font structs to LVGL font objects and local fmt_txt callbacks. Wire the new font names through C, CMake, Rust bindings, and tests, and remove the superseded uGUI font sources.
Show valid UTF-8 messages directly when every character is supported by the default BB02 font, falling back to hex otherwise. Truncate long displayable pages on UTF-8 boundaries so label bodies stay within the existing C label buffer limit.
Link the BB02 bootloaders against generated font subsets instead of the full firmware LVGL font data. The Arial subset is sliced from the checked-in arial_9.c data so the existing hand-edited glyph data is preserved for the ASCII range used by the bootloader.
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
from
8059edb to
14b9265
Compare
Collaborator
Author
|
Updates to the container are necessary, reopning from another branch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It should look exactly the same, I even applied our manual fixes to the 9px Arial. You can test unicode characters in message signing. For example, try signing
Zürich.I propose that we fix the truncation issues by migrating the label component to rust: #1974
The new font format is more efficient, so the Bootloader is about 700B smaller with the same character set. Firmware size is increased by 7kB