Timeline for answer to Console text UI progress bar in Java by TorbenPutkonen
Current License: CC BY-SA 4.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7 at 12:34 | comment | added | Toby Speight | The user can still choose a target of 1.0 if desired - so existing code using this class needs no change. The option to choose the scale helps simplify calling code by letting it work in its natural units,. | |
| Jul 7 at 9:32 | comment | added | TorbenPutkonen | Then you can add the possibility to modify the target after initialization. The common use case still is that the user knows an arbitrary total and the accumulated amount and the conversion is always the same. So it's better to not require the user to do it if they don't want. | |
| Jul 7 at 8:17 | comment | added | Basilevs | While I do see this in real libraries, they are quite inconvenient to use, as they require to determine the total amount of work to initialize progress bar. This forces unnatural flows, where a bunch of computation happens before common initialization steps. This is particularly annoying when initialization is required to determine the total work and there are many steps to it. | |
| Jul 7 at 5:56 | history | answered | TorbenPutkonen | CC BY-SA 4.0 |