Re: [webkit-dev] Proposed Timer API

2008-10-03 Thread Chris Marrin
On Oct 2, 2008, at 6:13 PM, Maciej Stachowiak wrote: On Oct 2, 2008, at 6:01 PM, Cameron McCormack wrote: Hi Maciej. Cameron McCormack: If possible, it would be nice if there could be some degree of compatibility between this proposed API and the one in SVG Tiny 1.2:

Re: [webkit-dev] Proposed Timer API

2008-10-03 Thread Geoffrey Garen
Hi Chris. I really like the idea of a Timer object. It would allow you to separate creation from starting, allows you to pause and add other API's to the interface. Can the constructor be used to simplify the creation: var t = new Timer(0, false, function() { ...}); which would start

Re: [webkit-dev] Proposed Timer API

2008-10-03 Thread Maciej Stachowiak
On Oct 3, 2008, at 11:01 AM, Chris Marrin wrote: On Oct 2, 2008, at 6:13 PM, Maciej Stachowiak wrote: On Oct 2, 2008, at 6:01 PM, Cameron McCormack wrote: Hi Maciej. Cameron McCormack: If possible, it would be nice if there could be some degree of compatibility between this proposed

Re: [webkit-dev] Proposed Timer API

2008-10-03 Thread Maciej Stachowiak
On Oct 3, 2008, at 11:15 AM, Geoffrey Garen wrote: Hi Chris. I really like the idea of a Timer object. It would allow you to separate creation from starting, allows you to pause and add other API's to the interface. Can the constructor be used to simplify the creation: var t = new

Re: [webkit-dev] Proposed Timer API

2008-10-03 Thread Chris Marrin
On Oct 3, 2008, at 1:48 PM, Maciej Stachowiak wrote: On Oct 3, 2008, at 11:01 AM, Chris Marrin wrote: On Oct 2, 2008, at 6:13 PM, Maciej Stachowiak wrote: On Oct 2, 2008, at 6:01 PM, Cameron McCormack wrote: Hi Maciej. Cameron McCormack: If possible, it would be nice if there could be

Re: [webkit-dev] Proposed Timer API

2008-10-03 Thread George Staikos
On 3-Oct-08, at 3:01 AM, Cameron McCormack wrote: Hi Maciej. Cameron McCormack: If possible, it would be nice if there could be some degree of compatibility between this proposed API and the one in SVG Tiny 1.2: http://dev.w3.org/SVG/profiles/1.2T/publish/ svgudom.html#svg__SVGTimer

Re: [webkit-dev] Proposed Timer API

2008-10-02 Thread Dmitry Titov
: Re: [webkit-dev] Proposed Timer API On Oct 1, 2008, at 9:58 AM, Darin Adler wrote: On Oct 1, 2008, at 9:16 AM, Mike Belshe wrote: If you're going to propose a new API designed for hi-res timers, it ought to use units of microseconds instead of milliseconds. Or units of seconds

Re: [webkit-dev] Proposed Timer API

2008-10-02 Thread Maciej Stachowiak
On Oct 1, 2008, at 9:11 PM, Cameron McCormack wrote: Justin Haygood: http://blog.justinhaygood.com/2008/09/30/proposed-high-resolution-timer-api/ If possible, it would be nice if there could be some degree of compatibility between this proposed API and the one in SVG Tiny 1.2:

Re: [webkit-dev] Proposed Timer API

2008-10-02 Thread Cameron McCormack
Hi Maciej. Cameron McCormack: If possible, it would be nice if there could be some degree of compatibility between this proposed API and the one in SVG Tiny 1.2: http://dev.w3.org/SVG/profiles/1.2T/publish/svgudom.html#svg__SVGTimer Maciej Stachowiak: I considered that, but I don't

Re: [webkit-dev] Proposed Timer API

2008-10-02 Thread Justin Haygood
-dev] Proposed Timer API Hi Maciej. Cameron McCormack: If possible, it would be nice if there could be some degree of compatibility between this proposed API and the one in SVG Tiny 1.2: http://dev.w3.org/SVG/profiles/1.2T/publish/svgudom.html#svg__SVGTimer Maciej Stachowiak: I

Re: [webkit-dev] Proposed Timer API

2008-10-01 Thread Mike Belshe
If you're going to propose a new API designed for hi-res timers, it ought to use units of microseconds instead of milliseconds. Mike On Tue, Sep 30, 2008 at 7:32 PM, Justin Haygood [EMAIL PROTECTED]wrote: http://blog.justinhaygood.com/2008/09/30/proposed-high-resolution-timer-api/ It's

Re: [webkit-dev] Proposed Timer API

2008-10-01 Thread Darin Adler
On Oct 1, 2008, at 9:16 AM, Mike Belshe wrote: If you're going to propose a new API designed for hi-res timers, it ought to use units of microseconds instead of milliseconds. Or units of seconds, perhaps? Since JavaScript numbers are already floating point. -- Darin

Re: [webkit-dev] Proposed Timer API

2008-10-01 Thread Maciej Stachowiak
On Oct 1, 2008, at 9:58 AM, Darin Adler wrote: On Oct 1, 2008, at 9:16 AM, Mike Belshe wrote: If you're going to propose a new API designed for hi-res timers, it ought to use units of microseconds instead of milliseconds. Or units of seconds, perhaps? Since JavaScript numbers are already

Re: [webkit-dev] Proposed Timer API

2008-10-01 Thread Justin Haygood
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maciej Stachowiak Sent: Wednesday, October 01, 2008 1:02 PM To: Darin Adler Cc: WebKit Development Subject: Re: [webkit-dev] Proposed Timer API On Oct 1, 2008, at 9:58 AM, Darin Adler wrote: On Oct 1

Re: [webkit-dev] Proposed Timer API

2008-10-01 Thread Alex Iskander
I first sent this to Mike Belshe; I meant to send it to the list, but I'm new to it: Perhaps it could use milliseconds, but allow floating-point numbers. Milliseconds would be easier, in my opinion, to work with than microseconds. Adobe's data type for delay is Number, which according to