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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <sebastien.requiem@gmail.com>) id 1WrMbJ-0007j1-V2
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Jun 2014 07:24:09 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175;
envelope-from=sebastien.requiem@gmail.com;
helo=mail-we0-f175.google.com;
Received: from mail-we0-f175.google.com ([74.125.82.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WrMbI-00073t-4x
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Jun 2014 07:24:09 +0000
Received: by mail-we0-f175.google.com with SMTP id p10so4586321wes.6
for <bitcoin-development@lists.sourceforge.net>;
Mon, 02 Jun 2014 00:24:01 -0700 (PDT)
X-Received: by 10.194.87.200 with SMTP id ba8mr47023763wjb.28.1401693841573;
Mon, 02 Jun 2014 00:24:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.24.231 with HTTP; Mon, 2 Jun 2014 00:23:41 -0700 (PDT)
In-Reply-To: <CADZB0_YZ==Kd-R10d996E=6X-VoVhyE0cvW=_LGXJvQLAbVUpw@mail.gmail.com>
References: <CADZB0_YZ==Kd-R10d996E=6X-VoVhyE0cvW=_LGXJvQLAbVUpw@mail.gmail.com>
From: sebastien requiem <sebastien.requiem@gmail.com>
Date: Mon, 2 Jun 2014 09:23:41 +0200
Message-ID: <CABLWKA-dsty-WsZmDw4=Js_utwNY4isOm8zW_u-70pN7bgHo3A@mail.gmail.com>
To: Angel Leon <gubatron@gmail.com>
Content-Type: multipart/alternative; boundary=089e010d8afe82cfc904fad547c0
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
(sebastien.requiem[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: 1WrMbI-00073t-4x
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [QT] Feature proposal: Displaying current
Units/Changing Units with status bar control.
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: Mon, 02 Jun 2014 07:24:10 -0000
--089e010d8afe82cfc904fad547c0
Content-Type: text/plain; charset=UTF-8
Hello Angel,
Good initiative. This looks good. If I understand, the dropdown menu is for
the whole application, so it make sense to have it in a common part of the
layout.
A slight optimisation would be to write the unit in the transaction table
header too (since we read from top to bottom). This would give something
like "Amount (mBTC)". That way, the user doesn't have to think twice about
the unit of his values.
Hope it helps,
On Fri, May 30, 2014 at 6:39 PM, Angel Leon <gubatron@gmail.com> wrote:
> There's been quite a lot of debate over the default unit of display to
> use, you can read the conversation here, which was closed.
> https://github.com/bitcoin/bitcoin/issues/3862
>
> Whatever the side of the debate you're on, wether it should be BTC or
> mBTC, or other, regular users will probably take too long to find a way to
> change the current unit of display, and if the unit of display were ever
> changed to something other than BTC, the current transaction tables"Amount"
> column don't mention anywhere what Unit of Display is being used.
>
> So last night I started playing with the idea of having a status bar
> component that would:
> 1. Show you what is the current unit of display at all times.
> 2. Let you change the unit of display easily.
>
> Here's how it looks (see attachment), just wanted to get feedback, if this
> is something you also consider valuable in terms of user experience, or
> maybe you don't want to allow any more controls on the status bar (because
> then people will want to add more and more)
>
> Just want to get some feedback before I continue working on this to polish
> it and submit a pull request.
>
>
> Cheers.
> Angel (@gubatron)
>
>
> ------------------------------------------------------------------------------
> Time is money. Stop wasting it! Get your web API in 5 minutes.
> www.restlet.com/download
> http://p.sf.net/sfu/restlet
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
sebastien requiem
--089e010d8afe82cfc904fad547c0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hello Angel,<div><br></div><div>Good initiative. This look=
s good. If I understand, the dropdown menu is for the whole application, so=
it make sense to have it in a common part of the layout.</div><div><br></d=
iv>
<div>A slight optimisation would be to write the unit in the transaction ta=
ble header too (since we read from top to bottom). This would give somethin=
g like "Amount (mBTC)". That way, the user doesn't have to th=
ink twice about the unit of his values.</div>
<div><br></div><div><br></div><div>Hope it helps,</div><div><br></div><div>=
<br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">On Fri, May 30, 2014 at 6:39 PM, Angel Leon <span dir=3D"=
ltr"><<a href=3D"mailto:gubatron@gmail.com" target=3D"_blank">gubatron@g=
mail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>There's been quite=
a lot of debate over the default unit of display to use, you can read the =
conversation here, which was closed.<br>
<a href=3D"https://github.com/bitcoin/bitcoin/issues/3862" target=3D"_blank=
">https://github.com/bitcoin/bitcoin/issues/3862</a><br>
<br>Whatever the side of the debate you're on, wether it should be BTC =
or mBTC, or other, regular users will probably take too long to find a way =
to change the current unit of display, and if the unit of display were ever=
changed to something other than BTC, the current transaction tables"A=
mount" column don't mention anywhere what Unit of Display is being=
used.<br>
<br>So last night I started playing with the idea of having a status bar co=
mponent that would:</div><div>1. Show you what is the current unit of displ=
ay at all times.</div><div>2. Let you change the unit of display easily.<br=
>
<br>Here's how it looks (see attachment), just wanted to get feedback, =
if this is something you also consider valuable in terms of user experience=
, or maybe you don't want to allow any more controls on the status bar =
(because then people will want to add more and more)</div>
<div><br></div><div>Just want to get some feedback before I continue workin=
g on this to polish it and submit a pull request.<br><br><br>Cheers.<br>Ang=
el (@gubatron)</div>
</div>
<br>-----------------------------------------------------------------------=
-------<br>
Time is money. Stop wasting it! Get your web API in 5 minutes.<br>
<a href=3D"http://www.restlet.com/download" target=3D"_blank">www.restlet.c=
om/download</a><br>
<a href=3D"http://p.sf.net/sfu/restlet" target=3D"_blank">http://p.sf.net/s=
fu/restlet</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>sebastie=
n requiem
</div>
--089e010d8afe82cfc904fad547c0--
|
