Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Sugggestion] Mabye use custom font for time? #1

Open
5 tasks
alni opened this issue Dec 14, 2017 · 1 comment
Open
5 tasks

[Sugggestion] Mabye use custom font for time? #1

alni opened this issue Dec 14, 2017 · 1 comment

Comments

@alni
Copy link
Owner

alni commented Dec 14, 2017

To give the watch face a more custom-made look, mabye test how a custom font would look like?

Requirements:

  • Sans-Serif
  • The numbers should have same upper and lower body style (e.x. the circles of the number "8" should be the same size)
  • The characters should be easily readable at a glanse (even with somewhat poor eye-sight)
    • The tickness should not be too thin, neither too thick
    • The width should not be too small or too large
    • No cursive/big slant; the characters should be aligned with x/y axis (no sway to either sides)
  • The fonts should be licensed under an open/permissive license and be free of charge that allows using with a open-source project

Here is a filtered list from Google Web Fonts that may meet these requirements

Fonts that does meet the requirements:

  • Roboto Condensed - acceptable thickness, good width even as condensed
  • Oswald - good thickness variations, acceptable width
  • Titillium Web - many good thickness variations, acceptable width

Fonts that does not meet the requirements:

  • Josefin Sans - the numbers does not have the same upper and lower body style (they will look strange on the watch)
  • Lato - same issue as with Josefin Sans (but not as apparent)
    • This one is a mabye. Needs to test on a real watch to make sure

TODO:

  • Check all fonts in the filtered lists at Google Web Fonts and include and document them if they meet the requirements or not
  • Test all fonts that meet the requirements in the simulator
  • All that looks good in the simulator should be tested on a real device
  • Strike-through all fonts that does not look good in the simulator
  • Then choose the most readable font from the real device testing
@alni
Copy link
Owner Author

alni commented Dec 16, 2017

Remember to install the font then select as font with the BMFont program (do not select the font file directly as additional font as this will result in the spacing of the characters to be wrong!)

alni added a commit that referenced this issue Dec 17, 2017
alni added a commit that referenced this issue Dec 17, 2017
For all devices (except the vivoactive_hr):

* use the same Teko ("TImeFont") font
* move the time labels a bit down, and a little more space between
  the hour and minute labels
- also move the date labels (where needed)

For the vivoactive_hr:

* create a smaller variant of the Teko ("TimeFont") font as the
  other version did not fit within the smaller width of the device
  screen
* move the "A" and "P/M" labels to below-right of the time labels -
  they did not fit on the right with the new font) and keep both
  the "A" and the "P/M" labels together on the same line
* move the date labels a bit further down, below the new position
  of the "A" and "P/M" labels
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant