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 asked that
> question on the GWT groups earlier and people seemed to be interested.
>
> Cheers, Jonas
>
> This is my first ever open source contribution so please give me
> comments and feedback on my blog or the project page.
>
> On Feb 10, 2:07 am, HaiColon wrote:
>
What I do is I write the gadget in a way that makes it work both
locally (or as a website on a remote server) and then I add a layer on
top that makes it work with Google Wave. That way I can test 90% of
the gadget locally, no problem. And for the other 10% I just use the
debug features of the sand
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
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
l receive multiple state callbacks, due to how the
> changes to the wave data model are processed. We will look into
> bundling the callbacks to make this a better experience for
> developers, however.
>
>
>
> On Sun, Jan 17, 2010 at 7:27 AM, HaiColon wrote:
> > Ah, I haven&#x
u can do something similar as
> a workaround for now?
>
> Best,
> --Justin
>
> On Jan 15, 8:23 pm, HaiColon wrote:
>
>
>
> > I'm actually submitting four things with each call to submitDelta(),
> > but I only get two callbacks instead of four so this c
e gadget in a single callback.
>
> Since the data I was submitting in my case was tightly coupled, I
> combined the data into a single JSON string value and submitted it in
> a single submitValue() call instead and it worked great.
>
> Hope this helps,
> --Justin
>
> On Ja
A Google Wave bug then. Thanks for answering :)
I'll file a bug report.
On Jan 14, 4:15 pm, Eyal wrote:
> I encountered the same behavior. What I did to work around it was to
> send a dummy first key and then the rest of the data, all as one
> delta.
>
> On Jan 14, 5:02
I'm currently writing a multiplayer Match 3 style game for Google Wave
(Match 3 = If three or more blocks/gems/whatever of the same color are
aligned horizontally or vertically, those blocks are destroyed, giving
you points. The blocks above the destroyed blocks fall down and the
now empty space at
Does this mean "a couple hours later" or "on another day" instead?
On 5 Nov., 00:13, "Austin Chau (Google employee)"
wrote:
> Yes this week office hour is changed to a different time than normal because
> a lot of us are travelling. Sorry for the inconvenience.
>
> Austin
--~--~-~--~---
Could you give me a link to the bugreport? I wasn't able to find it in
the bug tracker, I only found a report on newlines not working at the
start of a blip.
On Oct 6, 10:56 am, Paul Staab wrote:
> Thats a known Bug mentioned in the last Office Hours i think. I also
> wrote an Bugreport for it.
ngle time I log in. I guess my account got screwed up on creation
> but I have no idea how to get it fixed.
>
> Drak
>
> 2009/10/2 HaiColon :
>
>
>
>
>
> > I tried again just now and it seems to work fine again. Does it work
> > for you now too? If so, then I
I had hoped for the same thing as you did because I was finally able
to get my desired username on the wave sandbox :)
But see it the other way around. Imagine you had gotten your desired
username a long time ago with GMail. And then Google would let someone
else take it over through Wave, you'd
ontact someone at Google, let me know please.
>
> Regards,
>
> Drak
>
> 2009/10/2 HaiColon :
>
>
>
>
>
> > Worked fine half an our ago. Now when I try to open up the Google Wave
> > client on wave.google.com the shiny error pops up. Every time, with
> &g
Worked fine half an our ago. Now when I try to open up the Google Wave
client on wave.google.com the shiny error pops up. Every time, with
both Chrome (Linux dev channel) and Firefox 3.5.3.
Anyone else got this problem or is something wrong with my account? I
haven't actually done anything with t
16 matches
Mail list logo
