From: sebastien requiem <sebastien.requiem@gmail•com>
To: Angel Leon <gubatron@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [QT] Feature proposal: Displaying current Units/Changing Units with status bar control.
Date: Mon, 2 Jun 2014 09:23:41 +0200 [thread overview]
Message-ID: <CABLWKA-dsty-WsZmDw4=Js_utwNY4isOm8zW_u-70pN7bgHo3A@mail.gmail.com> (raw)
In-Reply-To: <CADZB0_YZ==Kd-R10d996E=6X-VoVhyE0cvW=_LGXJvQLAbVUpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 3119 bytes --]
next prev parent reply other threads:[~2014-06-02 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 16:39 Angel Leon
2014-06-02 7:23 ` sebastien requiem [this message]
2014-06-02 7:39 ` Wladimir
2014-06-02 7:54 ` Gregory Maxwell
2014-06-02 19:41 ` Angel Leon
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='CABLWKA-dsty-WsZmDw4=Js_utwNY4isOm8zW_u-70pN7bgHo3A@mail.gmail.com' \
--to=sebastien.requiem@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gubatron@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