[UX/UI redesign] Coloring and Grouping Numbers

[editwentyone]

tackling the following issues: #10518, #2588, #10609

key takeaways

• focus on one font, as soon as possible with avalonia (target font: Inter)
• colouring leading Zeros 0 different than the actual value
• use slashed Zeros 0 to distinguish between capital O
• use mono spaced version to format numbers, dates, time and hashes inside the whole app

🎨 Figma

wasabi_digits.mp4

[yahiheb]

• use slashed Zeros 0 to distinguish between capital O

I am not sure about this one.
Through out the whole video all the places where the slashed Zeros were used it was clear that it is a 0 not a capital O.

• When you are reading this number 113095 or 127.0.0.1:1833 or any price or any date there is no way that someone thinks it is a capital O.
• Seeing the address with slashed Zeros look confusing.

The original issue and confusion comes from the inconsistency and to solve that we can simply use normal 0 everywhere.

[editwentyone]

slashed zeros are slashing any confusion about 0, o and O. its either way: everywhere or nowhere, mixing is adding to the initial confusion.

its clear for the advanced user that 127.0.0.1 can never have O. but we are creating this software for a lot of different user personas with different skill level. one way to achieve consistency is: zeros are slashed, no matter where and in what context. or the other way around: no slashed zeros at all. doesnt matter where » problems with hashes and newbie users.

[yahiheb]

everywhere or nowhere, mixing is adding to the initial confusion.

That is my point, do not use it everywhere, specially in addresses.

we are creating this software for a lot of different user personas with different skill level. one way to achieve consistency is: zeros are slashed

Simple users might be confused with the slashed Zeros.

[MaxHillebrand]

This is excellent, cACK.

FYI, bech32 has the number 0, but not the letter O in it's character set to avoid confusions. So at least in address and amount we don't have to care about the confusing similarities.

[yahiheb]

FYI, bech32 has the number 0, but not the letter O in it's character set to avoid confusions. So at least in address and amount we don't have to care about the confusing similarities.

That was my reasoning too, and thus if we don't have it in addresses and amounts then we shouldn't have it anywhere for consistency and simplicity.

[nostitos]

Same thing, I don't like the crossed zeros, there is no possible confusion anyways.

The rest looks good, I like the grayed leading 0s

[editwentyone]

Again, there are users who like slashed zeros and there are others who don’t.

I don’t really care, just for that issue, we could flip a coin.

the rest like coloring, spacing and consistency are another story.

So who wants to decide the slashes zeros? ;)

[MaxHillebrand]

I just flipped a coin, and it landed on empty zero, so do NOT use a slashed zero, unless you are comfortable with defying the gods of chance.

[editwentyone]

[soosr]

FTR it is not possible until Avalonia implements support for font features, We might get it in 11.X.

[turbolay]

This new tool from mempool.space: https://mempool.space/tools/calculator
implemented the exact colouring scheme proposed here. See how clear it is!

[stale]

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nostitos]

@trubolay, yes looks great!

…

On Sat, Sept 16, 2023, 17:52 stale[bot] ***@***.***> wrote: This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — Reply to this email directly, view it on GitHub <#10838 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALSB6MBR6MT5OKAPUBH72O3X2YNSHANCNFSM6AAAAAAYYQSTMA> . You are receiving this because you commented.Message ID: ***@***.***>