1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1VhGuK-00047o-Kt
for bitcoin-development@lists.sourceforge.net;
Fri, 15 Nov 2013 10:45:48 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.46 as permitted sender)
client-ip=209.85.214.46; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f46.google.com;
Received: from mail-bk0-f46.google.com ([209.85.214.46])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VhGuJ-0005PB-OQ
for bitcoin-development@lists.sourceforge.net;
Fri, 15 Nov 2013 10:45:48 +0000
Received: by mail-bk0-f46.google.com with SMTP id u15so291437bkz.19
for <bitcoin-development@lists.sourceforge.net>;
Fri, 15 Nov 2013 02:45:41 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.78.5 with SMTP id zk5mr4135069bkb.25.1384512341317; Fri,
15 Nov 2013 02:45:41 -0800 (PST)
Received: by 10.204.71.206 with HTTP; Fri, 15 Nov 2013 02:45:41 -0800 (PST)
In-Reply-To: <52852C2D.9020103@gmail.com>
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
<52852C2D.9020103@gmail.com>
Date: Fri, 15 Nov 2013 11:45:41 +0100
Message-ID: <CA+s+GJCJvKagcRQ5L8agDn0370mS4jfayhTu7LE_tshM_sBkZQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Alan Reiner <etotheipi@gmail.com>
Content-Type: multipart/alternative; boundary=f46d041038a74ac30604eb34e601
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VhGuJ-0005PB-OQ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] moving the default display to mbtc
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 15 Nov 2013 10:45:48 -0000
--f46d041038a74ac30604eb34e601
Content-Type: text/plain; charset=UTF-8
Alan,
I highly recommend that if we make any move towards this, that the
> software show verification in both/all units.
>
> For instance, there should be 3 input fields, one for "BTC", one for
> "mBTC" one for "uBTC". As the user enters a value in one of the fields, it
> would automatically update the other fields with the converted value as
> they type. This makes it really difficult to get it wrong... if you're
> typing "10" into the BTC field, thinking it's mBTC, you'll see 10,000 mBTC
> showing up in the other box as you type. Similarly, it should display all
> units on all verification windows. Users may also use it for sanity
> checking conversion between units.
>
Good point - For me its too much clutter to show multiple boxes everywhere
(we already support unit conversion by changing the dropdown box in the
amount widget), but I'm going to make the verification dialog show the
totals in all three units. This will make people learn about other units
without having to choose them consciously.
Wladimir
--f46d041038a74ac30604eb34e601
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Alan,<div><br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
I highly recommend that if we make any move towards this, that the
software show verification in both/all units. <br>
<br>
For instance, there should be 3 input fields, one for "BTC", =
one for
"mBTC" one for "uBTC".=C2=A0 As the user enters a v=
alue in one of the
fields, it would automatically update the other fields with the
converted value as they type.=C2=A0 This makes it really difficult to g=
et
it wrong... if you're typing "10" into the BTC field, thi=
nking it's
mBTC, you'll see 10,000 mBTC showing up in the other box as you
type.=C2=A0 Similarly, it should display all units on all verification
windows.=C2=A0 Users may also use it for sanity checking conversion
between units.<br></div></blockquote><div><br></div><div>Good point - F=
or me its too much clutter to show multiple boxes everywhere (we already su=
pport unit conversion by changing the dropdown box in the amount widget), b=
ut I'm going to make the verification dialog show the totals in all thr=
ee units. This will make people learn about other units without having to c=
hoose them consciously.</div>
<div><br></div><div>Wladimir</div><div><br></div></div></div></div></div>
--f46d041038a74ac30604eb34e601--
|
