Date: Tue, 13 Apr 1999 11:56:36 -0700 From: Thomas Stephens <tas@stephens.org> To: current@FreeBSD.ORG Cc: "Matthew D. Fuller" <fullermd@futuresouth.com>, schuerge@wurzelausix.CS.Uni-SB.DE, John Polstra <jdp@polstra.com>, Thomas Stephens <tas@stephens.org> Subject: Re: cvsup Message-ID: <199904131856.TAA05150@stephens.ml.org> In-Reply-To: Your message of "Tue, 13 Apr 1999 08:29:30 PDT." <XFMail.990413082930.jdp@polstra.com>
index | next in thread | previous in thread | raw e-mail
John Polstra wrote: >Matthew D. Fuller wrote: >> >> As a data point, CVSup runs nicely, but if I iconify it and deiconify it, >> it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay >> itself completely. > >Yes, that's when the problem is most obvious. > >Here's the bottom line from my point of view. CVSup is slow to update >the GUI because it is busy doing more important things, i.e., updating >your files as quickly as it can. I agree that it can be annoying. >But would you really want me to slow down file updates just so the GUI >could look better? In my view, the non-GUI mode provides excellent feedback (depending on the level of verbosity), so I'd certainly prefer to see the focus remain speed, as opposed to the GUI. I seem to recall that a certain OS, which will remain nameless, used to spend more file-copy time calculating and updating progress bars than actually moving data (all controlled I/O, IIRC). It looked nice, was very responsive and the progress bars were smooth and accurate to the pixel, but it isn't the route I'd choose! (To be fair, this was probably a relic of the floppy-drive days.) Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904131856.TAA05150>