- From: Alex Danilo <alex@abbra.com>
- Date: Wed, 03 Sep 2008 08:02:05 +1000
- To: Erik Dahlstrom <ed@opera.com>
- Cc: anthony.grasso@cisra.canon.com.au, public-svg-wg@w3.org
Hi Erik, As Niklas pointed out, a stand alone SVG UA has the Timer interface as the only method for triggering timing. I don't see any real need to rename it as 'setTimeout' operates quite differently to Timer. Alex --Original Message--: > >If there are no external dependencies on Timer, I'd favor removing it from the spec, especially given that the Window object already provides timer functionality, and that it's also possible to produce customized timers using the animation elements. > >Cheers >/Erik > >On Tue, 02 Sep 2008 00:45:51 +0200, Anthony Grasso <anthony.grasso@cisra.canon.com.au> wrote: > >> Dude, >> >> Considering there is no external dependency on this, I think it will >> fine to go ahead with the change. >> >> Cheers, >> >> Anthony >> >> Cameron McCormack wrote: >>> Cameron McCormack via cvs-syncmail: >>>> Log Message: >>>> Rename global::Timer to svg::Timer. >>>> (Part of ACTION-2179) >>> >>> Now that Timer has moved from the soon to be extinct ‘global’ module to >>> the ‘svg’ module, I think it should be renamed SVGTimer. As mentioned >>> during the F2F, JSR 287 doesn’t have a dependency on the name since they >>> don’t include Timer. This wouldn’t change the syntax needed to create a >>> timer (which still would be createTimer(…)), but would just make the >>> naming more consistent. >>> >>> Thanks, >>> >>> Cameron >>> >> >> > > > >-- >Erik Dahlstrom, Core Technology Developer, Opera Software >Co-Chair, W3C SVG Working Group >Personal blog: http://my.opera.com/macdev_ed > > > >
Received on Tuesday, 2 September 2008 22:03:00 UTC