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. The actual time countdown would be done in Javascript, and be based on a calculation of the start time, current time, and timer duration.
- pamela On Mon, Feb 8, 2010 at 11:59 AM, qMax <[email protected]> wrote: > At http://googlewavedev.blogspot.com/2010/02/my-extension-wish-wave-timer.html > Anna-Christina Douglas wrote: >> I would love a collaborative timer, clock, or stopwatch that I could put at >> the top of a wave when the meeting starts. > > being implemented as a gadget, the timer will be updated in every > instance of the gadget. > which is quite wrong thing. > > One way is: > The gadget raise an election among gadget instances to select which > instance will update the timer. > The election should be reraised when the instance is closed - but how > to determine this event? > > Another way: > The timer is updated by robot and the time propagated to the gadget. > This requires cron events for every, say, second. This looks > overwhelming. > And is it yet possible to update a wave by cron, rather then as > ersponce to event? > > -- > You received this message because you are subscribed to the Google Groups > "Google Wave API" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-wave-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
