public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Rodolfo Novak <rodolfo@coinkite•com>
To: damgaard.martin@gmail•com,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion for a universal bitcoin value scale
Date: Sun, 19 Aug 2018 07:42:13 -0400	[thread overview]
Message-ID: <7EA432A9-BF76-4B2A-B664-0F374BD5C18F@coinkite.com> (raw)
In-Reply-To: <5b787d19.1c69fb81.e0628.771a@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

This is not a good solution. In UX colors have expected meaning. Red often means error, yellow cation, green possible, etc... 

Text doesn’t have good legibility in colors, monochrome high contrast being the best.

You will also have issues with colorblind people.

Rodolfo 

ℝ.

> On Aug 18, 2018, at 16:10, Martin Damgaard via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
> Hi bitcoin-dev@lists•linuxfoundation.org
> Here is my humble attempt to make a contribution to the impressive work that you all are doing.
> I am unfamiliar with the normal BIP procedures. I have therefore just tried to follow the example of BIP 176 by Jimmy Song, in order make something similar. I suggest a universal bitcoin value color scale, for tackling the same decimal problem, as identified by the BIP 176 proposal.
> I have attached the document in three different formats (*.rtf, *.pdf and *.docx) as I do not know your preferred format. I hope you will find my suggestion useful.
>  
> Thank you and all the best
> Martin Damgaard
> <Universal bitcoin value color scale.rtf>
> <Universal bitcoin value color scale.pdf>
> <Universal bitcoin value color scale.docx>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

[-- Attachment #2: Type: text/html, Size: 3823 bytes --]

  reply	other threads:[~2018-08-19 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-18 20:10 damgaard.martin
2018-08-19 11:42 ` Rodolfo Novak [this message]
     [not found] ` <CAJS4p67a+47PimeSizBsAb9nanjaOdgB41hDQXoKFj9OxMqMFA@mail.gmail.com>
2018-08-19 14:21   ` damgaard.martin
2018-08-20 23:36 ` rhavar
2018-09-12  6:13 ` Karl-Johan Alm
2018-09-12  6:32   ` damgaard.martin
2018-09-12 14:54     ` Clark Moody

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7EA432A9-BF76-4B2A-B664-0F374BD5C18F@coinkite.com \
    --to=rodolfo@coinkite$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=damgaard.martin@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox