One more thing- please make an installer for it so that it is easier to
share.
On Thu, Feb 18, 2010 at 10:49 AM, pamela (Google Employee) <
pamela...@gmail.com> wrote:
> Hey Chris -
>
> Thanks for sharing the timer, I showed it to the blog post author to try
> out. Here's her feedback on improvem
Hey Chris -
Thanks for sharing the timer, I showed it to the blog post author to try
out. Here's her feedback on improvements that can be made:
- When in Stopwatch mode, the buttons should be start and stop--so that it
doesnt toggle between timer and stopwatch
- The blinking is slightly annoying
Here is my current implementation of this if anyone wants to try it
out in a wave:
http://colongadgets.appspot.com/gadgets/timealready/timealready.xml
Usage:
--
Eggtimer mode
Enter something like...
5 minutes
1 hour 20 seconds
2 hours and 30 seconds
4 seconds, 20 minutes
1h5m2s (this is
I think you can work around that. First, if there is a 300 ms delay
from the server response, the timer would be off by 600 ms total and I
don't think that anyone cares about half a second. The time to press
the stop button is well over half a second already unless you hover
over the stop button be
There are obvious technical problems related to the stopwatch
synchronicity and latency on various participants' screens (pings of
over 300ms between Sydney and US are common due to switch and repeater
loads, even though light should cross the pacific over fibre in about
6ms). Further complications
Wouldn't the timer be off every time the browser/computer freezes if
you use a timer duration in the calculation and just count the ticks?
If your browser freezes for a second, the timer is off by a second. If
it freezes for 5 seconds, it's off by 5 seconds.
What I did is I store the start time of
It's a service I set up for the last post.
Here's the code:
import time
if __name__ == '__main__':
print "Cache-Control: no-cache, must-revalidate"
print "Content-type: text/plain\n"
print time.time()
Eyal.
On Mon, Feb 8, 2010 at 2:33 PM, pamela (Google Employee) <
pamela...@gmail.com> wro
Agreed, I was just thinking the same thing. Is that your App Engine
app? (Will it remain up as a reliable service?)
Thanks for sharing the code!
On Mon, Feb 8, 2010 at 7:49 PM, eyalzh wrote:
> The way I see it, to overcome the differences between local clocks you must
> use a robot or a web serv
The way I see it, to overcome the differences between local clocks you must
use a robot or a web service that will tell you the time.
The gadget will make a request to that service whenever it is rendered by a
client. Thereafter it will just tick using javascript.
Here is an example of such a serv
[sorry for fingeroughness]
i'ts quite reasonable to make installer gadget instance to alarm
robot,
in hope that installer/moderator will not close the wave or
disconnected beforehand.
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post t
On 8 фев, 07:22, "pamela (Google Employee)"
wrote:
> My idea -
>
> If it was done strictly as a gadget, then the gadget would just store
> the time that a timer started, and the duration of the timer. Then,
> the wave would only be updated when someone set a new timer -- which
> makes sense to me.
11 matches
Mail list logo
