offload notification fonts to sender #2444
Replies: 2 comments
|
I think there's another issue tracking something like this somewhere already. There's also the suggestion that characters can be loaded from external flash, and the user can drop in fonts containing the languages they care about. Both are things being considered. Regarding your suggestion specifically though, the problem is that it requires completely changing the way notifications are sent. Sending a string of bitmaps over for a notification rather than a simple array of bytes for the characters is a very different operation. It would take a lot of work to support this in both InfiniTime and in companion apps |
|
May be worth noting that for Apple devices, notifications are delivered directly to the watch from the phone; companion app is not involved. Therefore, a dual approach might be necessary (possibly combined with letting the user choose which notification system they want in their firmware at build time) |
Uh oh!
There was an error while loading. Please reload this page.
There was an issue about it that was closed as not planned, but please reconsider adding the feature to load notifications as bitmap, the divergence from that suggestion is that I propose letting the sender send a bitmap and for InfiniTime to just display it, that way there are less constraints because there is no need to convert charterers on device so we don't need to store all the international fonts to support all languages just bitmap support.
dare I say it may free up some space because you won't need to support notification rendering beyond the bitmap, so you can remove all non-basic ASCII like emojis that you won't use in the UI itself. Although it is debatable if you want to outright remove the current system perhaps a dual approach will be better, I don't know enough to tell.
All reactions