[arch-projects] Pacman improvement
this as probably been posted before but here's my idea:
Instead of current [################] 100% 38K 14.2K/s 00:00:02 extra [################] 100% 147K 14.8K/s 00:00:10
We should change pacman to Instead of current [C...............] 0% 38K 14.2K/s 00:00:02 Instead of current [ C........] 50% 38K 14.2K/s 00:00:02 current [ C...] 75% 147K 14.8K/s 00:00:10 Current [ C] 100% 147K 14.8K/s 00:00:10
Just to reflect the name.
__________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
On Tue, 24 Aug 2004 19:14:39 -0700 (PDT), Tim Goff goffa@yahoo.com wrote:
this as probably been posted before but here's my idea:
Instead of current [################] 100% 38K 14.2K/s 00:00:02 extra [################] 100% 147K 14.8K/s 00:00:10
We should change pacman to Instead of current [C...............] 0% 38K 14.2K/s 00:00:02 Instead of current [ C........] 50% 38K 14.2K/s 00:00:02 current [ C...] 75% 147K 14.8K/s 00:00:10 Current [ C] 100% 147K 14.8K/s 00:00:10
Just to reflect the name.
I'm afraid I don't quite understand what you're getting at. Could you explain a little more?
Ok.. i made myself unclear... was trying to show the progress bar of pacman while its running.
I suggest having C..... for a progress bar rather than ###### and then have the C "eat the dots" so to speak.
I realize that pacman stands for package management, but just as a novelty i think we should change the progress bar to C... Just to reflect the name similarity with the game.
Not a functionality improvement, just a novelty. Does that make sense? If not, i can try to explain again.
Thanks for your fast response,
Tim
--- Michael Baehr mbaehr@gmail.com wrote:
On Tue, 24 Aug 2004 19:14:39 -0700 (PDT), Tim Goff goffa@yahoo.com wrote:
this as probably been posted before but here's my idea:
Instead of current [################] 100% 38K 14.2K/s 00:00:02 extra [################] 100% 147K 14.8K/s 00:00:10
We should change pacman to Instead of current [C...............] 0% 38K 14.2K/s 00:00:02 Instead of current [ C........] 50% 38K 14.2K/s 00:00:02 current [ C...] 75% 147K 14.8K/s 00:00:10 Current [ C] 100% 147K 14.8K/s 00:00:10
Just to reflect the name.
I'm afraid I don't quite understand what you're getting at. Could you explain a little more?
-- Michael Baehr - Arch Linux GNUstep Geek
arch-projects mailing list arch-projects@archlinux.org http://archlinux.org/mailman/listinfo/arch-projects
_______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com
On Tue, 24 Aug 2004 19:37:45 -0700 (PDT), Tim Goff goffa@yahoo.com wrote:
Ok.. i made myself unclear... was trying to show the progress bar of pacman while its running.
I suggest having C..... for a progress bar rather than ###### and then have the C "eat the dots" so to speak.
I realize that pacman stands for package management, but just as a novelty i think we should change the progress bar to C... Just to reflect the name similarity with the game.
Not a functionality improvement, just a novelty. Does that make sense? If not, i can try to explain again.
Thanks for your fast response,
Tim
I think it's kinda cute. Dunno if Judd's for it, but hey :P
Ok.. i made myself unclear... was trying to show the progress bar of pacman while its running.
I suggest having C..... for a progress bar rather than ###### and then have the C "eat the dots" so to speak.
I realize that pacman stands for package management, but just as a novelty i think we should change the progress bar to C... Just to reflect the name similarity with the game.
Not a functionality improvement, just a novelty. Does that make sense? If not, i can try to explain again.
Thanks for your fast response,
Tim
--- Michael Baehr mbaehr@gmail.com wrote:
On Tue, 24 Aug 2004 19:14:39 -0700 (PDT), Tim Goff goffa@yahoo.com wrote:
this as probably been posted before but here's my idea:
Instead of current [################] 100% 38K 14.2K/s 00:00:02 extra [################] 100% 147K 14.8K/s 00:00:10
We should change pacman to Instead of current [C...............] 0% 38K 14.2K/s 00:00:02 Instead of current [ C........] 50% 38K 14.2K/s 00:00:02 current [ C...] 75% 147K 14.8K/s 00:00:10 Current [ C] 100% 147K 14.8K/s 00:00:10
Just to reflect the name.
I'm afraid I don't quite understand what you're getting at. Could you explain a little more?
-- Michael Baehr - Arch Linux GNUstep Geek
arch-projects mailing list arch-projects@archlinux.org http://archlinux.org/mailman/listinfo/arch-projects
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Tue, 2004-08-24 at 21:32, Michael Baehr wrote:
I'm afraid I don't quite understand what you're getting at. Could you explain a little more?
You're quite daft sometimes. :P
Also, it might be better to have an alternation of big C and little c, to show a "chomping" motion.
Oh, and it should be written in Python.
Ben
On Tue, Aug 24, 2004 at 07:14:39PM -0700, Tim Goff wrote:
this as probably been posted before but here's my idea:
Instead of current [################] 100% 38K 14.2K/s 00:00:02 extra [################] 100% 147K 14.8K/s 00:00:10
We should change pacman to Instead of current [C...............] 0% 38K 14.2K/s 00:00:02 Instead of current [ C........] 50% 38K 14.2K/s 00:00:02 current [ C...] 75% 147K 14.8K/s 00:00:10 Current [ C] 100% 147K 14.8K/s 00:00:10
Just to reflect the name.
I hate to say this, but I don't think this is technically interesting or really all that difficult to do. A patch could be written very easily, even by you, to implement something like this and submit it as a bug.
I think a request like this should go to the regular arch mailing list.
Jason
I'm new to arch, didn't know where to send this. I just took some advice from the #archlinux chan.
And um... you say the code could be written even by you. It probably could, but i don't know how. That's why i posted this.
--- Jason Chu jason@archlinux.org wrote:
On Tue, Aug 24, 2004 at 07:14:39PM -0700, Tim Goff wrote:
this as probably been posted before but here's my idea:
Instead of current [################] 100%
38K 14.2K/s 00:00:02 extra [################] 100%
147K 14.8K/s 00:00:10
We should change pacman to Instead of current [C...............] 0%
38K 14.2K/s 00:00:02 Instead of current [ C........] 50%
38K 14.2K/s 00:00:02 current [ C...] 75%
147K 14.8K/s 00:00:10 Current [ C] 100%
147K 14.8K/s 00:00:10
Just to reflect the name.
I hate to say this, but I don't think this is technically interesting or really all that difficult to do. A patch could be written very easily, even by you, to implement something like this and submit it as a bug.
I think a request like this should go to the regular arch mailing list.
Jason
-- If you understand, things are just as they are. If you do not understand, things are just as they are.
My old gpg key expired, the new one is available from keyservers. I was stupid enough not to realize this before it was too late, so I am not able to sign my new key with my old key. If this assurance isn't enough, please contact me.
ATTACHMENT part 2 application/pgp-signature
_______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush
What's up, guys.
diff -Naur orig/pacman-2.8.4/src/pacsync.c pacman-2.8.4/src/pacsync.c --- orig/pacman-2.8.4/src/pacsync.c 2004-07-16 20:16:35.000000000 -0500 +++ pacman-2.8.4/src/pacsync.c 2004-08-25 03:00:31.000000000 -0500 @@ -57,6 +57,12 @@ extern PMList *pmc_syncs; extern int maxcols;
+/* hot hot pacman action */ +unsigned int lastcur = 0; +struct mouth { + unsigned open:1; +} mouth; + int sync_synctree() { char ldir[PATH_MAX] = ""; @@ -424,13 +430,17 @@ printf(" %s [", sync_fnm); cur = (int)((maxcols-64)*pct/100); for(i = 0; i < maxcols-64; i++) { - (i < cur) ? printf("#") : printf(" "); + (i < cur) ? printf(" ") : (i == cur) ? ((lastcur == cur) ? + (mouth.open ? printf("C") : printf("c")) : + (++mouth.open ? printf("C") : printf("c"))) : + printf("."); } if(rate > 1000) { printf("] %3d%% %6dK %6.0fK/s %02d:%02d:%02d\r", pct, ((xfered+offset) / 1024), rate, eta_h, eta_m, eta_s); } else { printf("] %3d%% %6dK %6.1fK/s %02d:%02d:%02d\r", pct, ((xfered+offset) / 1024), rate, eta_h, eta_m, eta_s); } + lastcur = cur; fflush(stdout); return(1); }
Because certain things sync so quickly, it's better if our pacman buddy leaves a trail. And I find that he prefers eating asterisks to dots.
s/printf(" ")/printf("-") s/printf(".")/printf("*")
Yeah.
Ok... and yeah asterisks are better :)
Ya gotta take care of him and feed him what he likes. --- Michael Baehr mbaehr@gmail.com wrote:
Because certain things sync so quickly, it's better if our pacman buddy leaves a trail. And I find that he prefers eating asterisks to dots.
s/printf(" ")/printf("-") s/printf(".")/printf("*")
Yeah.
-- Michael Baehr - Arch Linux GNUstep Geek
arch-projects mailing list arch-projects@archlinux.org http://archlinux.org/mailman/listinfo/arch-projects
_______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush
On Wed, 2004-08-25 at 02:15, Michael Baehr wrote:
Because certain things sync so quickly, it's better if our pacman buddy leaves a trail. And I find that he prefers eating asterisks to dots.
Pacman eats dots, anything else is blasphemy.
Ben
participants (4)
-
Ben Mazer
-
Jason Chu
-
Michael Baehr
-
Tim Goff