Skip Menu |

This queue is for tickets about the Devel-Comments CPAN distribution.

Report information
The Basics
Id: 72934
Status: open
Priority: 0/
Queue: Devel-Comments

People
Owner: xiong [...] cpan.org (daily)
Requestors: MITHALDU [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in:
  • v1.1.0
  • v1.1.1
  • v1.1.2
  • v1.1.3
  • v1.1.4
Fixed in: (no value)



Subject: [Feature] Please make it possible to disable the printing of a newline at progressbar end
When using many progress bars in a script, the screen fills up with many needless empty newlines, caused by an additional newline being printed after a progress bar is done. It would be nice if that could be disabled.
Subject: [Feature] please make it possible to enable updating of while progress bar even if there's no length change
The progress bar of while loops becomes almost static after ~2000 iterations due to a check that skips updates then the length doesn't change. It would be nice if i could disable that so i would at least see the numbers update. (If anything it should only check if the line itself changed and skip if that didn't happen.)
Subject: [Feature] Progress bar improvements
MITHALDU, Sorry for the delay in picking this up. I merged both tickets since they both relate to the same underlying feature. I'd like to think about both together and also an idea I've had simmering in my own mind. I had not planned to support progress bars as they are in 1.1.4 (as offered in Smart::Comments) into the 2.0.0 release. Most devs I talk to call them eye candy and I never use them myself. That's not to say I'm totally against them; I'm glad to hear another viewpoint. But as is, I think they simply offer too many alternatives (their documentation takes up half the POD of S::C) for too little actual function. Especially, they adapt poorly to the disk file output that motivated D::C. Now my vague idea was to offer some sort of more operational progress indicator: something that would not hog screen, disk, code, or POD. This would change 'deliberately vague' to precise and accurate, within realistic limits; in keeping with an intent of D::C as a serious, if lightweight, debugging tool. None of this conflicts with your expressed needs. Since I have something of a blind spot in this direction, I'd greatly appreciate it if you were willing to join me for some back-and-forth informal discussion of your needs, my concerns, and see if we can agree on a progress indicator feature set. Then I'll have a goal, which we can bring back to RT, to measure my own progress on implementation. Please let me know if you can sit down on this. I'm always on irc.freenode.org and irc.perl.org but we can do mailing list if you prefer. It's also possible to use the wiki on github. I'd like to leave the door open to other interested parties. Thanks, XIONG