Looks nice. But just leave the thing as GB please. I hate the pedantic GiB thing. No normal user will ever have heard of it. Heck even geeks like us need it explained to them constantly.
Convert the values to GB first if you're really adverse to displaying the wrong unit, then everyone wins.
12 Comments:
Wouldn't it be a good idea that the graphical representation of disk space be at the same scale *across* the different disks ?
It's strange seeing "7GB free" and "53GB free" taking up just about the same space ...
small comment:
GB is GigaBit.
Perhaps better use Gb or GiB? :)
Dimitry: GB is for gigabyte, Gb is for gigabit, so everything seems to be right.
@dmitry
GB is Gigabyte not GigaBit (1000^3 bytes)
GiB is Gibibyte (1024^3 bytes)
and Gb is used for GigaBits
More at http://en.wikipedia.org/wiki/Gigabyte
Ah, ok, thanks gyus.
Partly misunderstood :)
Looks nice. But just leave the thing as GB please. I hate the pedantic GiB thing. No normal user will ever have heard of it. Heck even geeks like us need it explained to them constantly.
Convert the values to GB first if you're really adverse to displaying the wrong unit, then everyone wins.
As someone who's been in engineering, I have to say the difference between GiB and GB is important.
If you choose to stay with GB, because we're all stupid (like leo s said), then at least make sure it's used correctly.
Just use the method KLocale::formatByteSize(). It will relieve you from the decision GB or GiB. :)
Applet now uses
KLocale::formatByteSize().
Are you using declarative animations in all of the widgets ?
No animation used.
THanks good work
Kompresör
Post a Comment
<< Home