I'm giving that a go now. It may take some time, though...
Thanks!
This is beautiful. Once you have this tested on Windows (and have tested it throughly) you should submit a pull request for this. I think that the mainstream client really ought to use QT (plus your GUI is so much nicer looking).
Yep, integrating this into the original client is planned after some build-system related issues have been sorted out there.
8 connections should be 2 bars, and 16+ should be 4
Why the 16+ requirement for 4? The mapping is currently like this;
- 0 -> No connection
- 1-3 -> 1 bar
- 4-6 -> 2 bars
- 7-9 -> 3 bars
- 10+ -> 4 bars
Great job!
Suggestion: get rid of the "Sent/Received" tab and keep just "All Transactions", "Sent" and "Received". Generated coins could be considered "received", you just change the Type to make it clear the difference.
This would be an improvement; however, I don't like the tabs at all.
Ideally it would be best to have a more extensive filter system; things like this should be possible
- show me transactions between 28/04/2010 and 28/06/2010
- show all transactions larger than 1.00 bitcoins
- show all transactions received with/sent to address XX
But I'm not entirely sure how to implement this without making it too complex and user-unfriendly. So a query language is out of the question :-)
Maybe add combo boxes in the header row like in spreadsheets?
I think it would be better to have the type column right-aligned, because of the way it reads. (type's text makes more sense with an adress next to it.)
May be true. Though right-aligned text columns might look weird. I'll give it a try.