How about something like this? This way it doesn't get displayed for the
quick updates.
function doServerUpdate() {
var serverUpdateTimer = setTimeout("showServerUpdateWait()", 5000);
...
hideServerUpdateWait();
clearTimeout(serverUpdateTimer);
}
David A. Green
(480) 813-1725
DAG Consulting
-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dawn Wolthuis
Sent: Wednesday, May 02, 2012 7:08 AM
To: U2 Users List
Subject: Re: [U2] READU vs READ and CRT
You are correct that the animated gif does not harm the processing time on
the server. I think it is obnoxious to the user when it is there for too
short a time, so I hauled some out and stopped putting them in, figuring we
will wait to see where they are really needed once we do volume testing. I
have not researched it to see if there are any studies that suggest that an
animated gif that flashes quickly provides a bad user experience. My UX
testing in this case was not formal -- it was me going "oh, yuck, I don't
want that gif to be there for so short a time."
You are right that this is not of the same ilk regarding performance. Yes,
it only shows while the server is doing something -- when a process returns
it hides the gif. --dawn
On Wed, May 2, 2012 at 8:21 AM, George Gallen
<ggal...@wyanokegroup.com>wrote:
> For a webapp, does an animated gif really detract processing time? The
> gif should be running client side, And the "processing" of the app
> would be running server side. Maybe you could only show the gif while
> The app is waiting for the server to push some more data?
>
> George
>
> -----Original Message-----
> From: u2-users-boun...@listserver.u2ug.org [mailto:
> u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
> Sent: Tuesday, May 01, 2012 8:38 PM
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] READU vs READ and CRT
>
>
> It's better for peace of mind to know that the computer thinks it's
> doing something Rather than wondering "Is it DOING something????"
>
>
>
>
> -----Original Message-----
> From: Dawn Wolthuis <dw...@tincat-group.com>
> To: U2 Users List <u2-users@listserver.u2ug.org>
> Sent: Tue, May 1, 2012 5:30 pm
> Subject: Re: [U2] READU vs READ and CRT
>
>
> Well, I get it even if it seems foolish at first blush -- it's all
> about he user experience. --dawn On Tue, May 1, 2012 at 7:24 PM,
> Charlie Noah <cwn...@comcast.net> wrote:
> > Hi Laura and Dawn,
>
> This reminds me of a program I wrote about 20 years ago for a
> multilevel marketing company. Its job was to audit a seller's
> downline, which in many cases ran into thousands or tens of thousands
> of transactions. For some larger sellers it ran for several minutes.
> The users insisted on seeing what progress it was making, and settled
> on a whirly-gig. I explained that it would only slow the process
> down, but they didn't care. They were quite willing to sacrifice speed
for a stupid little character twirling around.
> Go figure...
>
> Regards,
> Charlie Noah
>
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
--
Dawn M. Wolthuis
Take and give some delight today
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
