Timeline for Display big numbers in a small area
Current License: CC BY-SA 3.0
28 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2013 at 12:15 | comment | added | leftaroundabout | @Kaz: that's usually done when the font is tiny, obviously quite common in electronics etc. – but otherwise, it does just look wrong. As for 128K memory: those are probably kibibytes rather than kilobytes, so you can't really compare it to the situation here. | |
| Jun 5, 2013 at 8:31 | history | protected | JonW♦ | ||
| Jun 5, 2013 at 7:42 | answer | added | Mark Simpson | timeline score: 0 | |
| Jun 4, 2013 at 18:38 | vote | accept | GETah | ||
| Jun 4, 2013 at 18:05 | comment | added | Val | It is called "scientific notation". Floating points are based on that. You could start by implementing a default format and, then, add options for user to choose from. | |
| Jun 4, 2013 at 3:11 | comment | added | Kaz | There is definitely a tradition of using capital K for kilo, when the units are understood. Memory: 128K. Frequency: 3.8K denotes 3800 Hz. Resistance: 2.2K resistor is 2200 ohms. GETah did not just pull this out of thin air. I'd keep this as K and tell the naysayers to go look at the faceplate of an equalizer. Mine goes from 20 to 800, and after that 1K, 1.25K, 1.6K, ... , 20K. | |
| Jun 4, 2013 at 1:28 | comment | added | detly |
Who remembers the MARQUEE HTML tag?
|
|
| Jun 3, 2013 at 23:11 | answer | added | steeveeet | timeline score: 2 | |
| Jun 3, 2013 at 19:36 | answer | added | DJClayworth | timeline score: 11 | |
| Jun 3, 2013 at 19:33 | answer | added | BTestQ | timeline score: -2 | |
| Jun 3, 2013 at 16:03 | history | edited | rk. |
edited tags
|
|
| Jun 3, 2013 at 14:46 | comment | added | Caleb |
If you do use "k", please not that upper case is inappropriate for this. A lower case k is much more appropriate.
|
|
| Jun 3, 2013 at 14:46 | answer | added | Itai Sagi | timeline score: 33 | |
| Jun 3, 2013 at 14:40 | comment | added | Vince Bowdren |
If you need all the boxes to be the same width, that sounds like you're displaying data in a tabular format. If so, then use a <table>-based design: it's the right thing to do, and gives you benefits like automatically resizing columns to fit the contents in every row.
|
|
| Jun 3, 2013 at 12:21 | answer | added | rk. | timeline score: 66 | |
| Jun 3, 2013 at 11:51 | comment | added | Awesh | Accounting apps should display exact amount.. i would prefer to increase size of the box.. | |
| Jun 3, 2013 at 10:55 | history | tweeted | twitter.com/#!/StackUX/status/341508543612076032 | ||
| Jun 3, 2013 at 10:09 | comment | added | dav_i | @GETah I was more making a quip on incorrect SI usage! My view on this is that you should use "k" - people are used to it in the context of 1km = 1000m etc. | |
| Jun 3, 2013 at 10:05 | comment | added | GETah |
@dav_i Excellent user feedback!!! This is why I am hesitating to use the K
|
|
| Jun 3, 2013 at 10:04 | comment | added | dav_i | Why are you measuring price in Kelvin? | |
| Jun 3, 2013 at 9:23 | answer | added | bendur | timeline score: 1 | |
| Jun 3, 2013 at 9:22 | answer | added | Melroy Coelho | timeline score: 8 | |
| Jun 3, 2013 at 9:21 | review | First posts | |||
| Jun 3, 2013 at 9:24 | |||||
| Jun 3, 2013 at 9:21 | comment | added | AndroidHustle | Utilizing the K abbreviation is probably what I would go for, and then have a details view where the exact price is displayed. Disregarding that, why don't you justify the text from the center? If you let the text in the label be center aligned the 123336 figure in the image would fit. Of course that is a temporary solution since 7-8 figure prices would still pose a problem. | |
| Jun 3, 2013 at 9:20 | answer | added | peterchen | timeline score: 6 | |
| Jun 3, 2013 at 9:19 | answer | added | Alexey Kolchenko | timeline score: 38 | |
| Jun 3, 2013 at 9:12 | comment | added | Terry | Do you have any limitations? It makes a lot difference if you have total freedom in how you can solve this. | |
| Jun 3, 2013 at 9:04 | history | asked | GETah | CC BY-SA 3.0 |