Hi,
> Alexey Proskuryakov wrote:
> One way to come up with a good name for something already in existence is to
> look how other people call it. For example, a Wikipedia article on USB HID
> devices puts everything this spec cares about into "game controllers"
> section. How about GameController?
2011/10/12 Alexey Proskuryakov :
>
> The issues that I see are:
>
> - Immaturity that's manifesting itself even in the name. You can't really ask
> someone to meaningfully review a spec when its scope is so unclear.
What about the scope is unclear? I feel that the Scope section of the
spec and th
Hi Alexey,
The first revision of the spec (from the Scope section) is intended to
handle:
... support for devices common to current gaming systems including gamepads,
directional pads, joysticks, wheels, pedals, accelerometers.
This is based on a somewhat generic treatment of axes and buttons t
rg/hg/webevents/raw-file/tip/gamepad.html
scott
On Thu, Aug 25, 2011 at 8:44 AM, Scott Graham wrote:
> Thanks Simon and Dimitri, I wasn't familiar with the procedure for
> attacking these sorts of things.
>
> I've started a discussion on public-webapps, which will hopefully h
2011/9/21 Alexey Proskuryakov :
>
> platforms. Interfering with mouse movement would be one of the most
> dangerous and frustrating things Web pages could possibly do.
While I agree, that doesn't seem like a problem with the spec. As I
read the spec, it seems that it leaves enough latitude to allo
I believe the Windows ones are the .def files. I had to make a similar
change here: https://bugs.webkit.org/attachment.cgi?id=102529&action=prettypatch
(e.g. Source/WebKit2/win/WebKit2.def and similar)
You have to be able mangle in your head it seems. I found the easiest
way was to make a simple p
nts.
>>
>> I'd prefer a more general strategy of thinking about all the various types
>> of input events (e.g. joysticks, remote controls, assistive devices), and
>> having an API that caters for all of them. This of course would require
>> significant W3C
On Wed, Aug 24, 2011 at 9:19 AM, Simon Fraser wrote:
> I think it's too early to implement this. We should wait until it's a W3C
> draft at least.
There's certainly work to be done in improving the design. I'm not proposing
to slavishly implement the API exactly as specified there.
However, I w
Hi,
I wanted to let everyone know that I propose to add a new feature
flag, JOYSTICK. http://webkit.org/b/66859
This flag will enable an API and events for accessing joysticks and
related devices. There's a prototype effort happening in Mozilla also
(https://wiki.mozilla.org/JoystickAPI), and the
On Wed, Jul 27, 2011 at 12:15 PM, Simon Fraser wrote:
> On Jul 27, 2011, at 11:14 AM, Scott Graham wrote:
> > Does anyone disagree that all updates should use the same elapsed time
> during the update? Or, in other words, is there any reason to re-get the
> current wallclock
Hi,
When the Timer is fired for SMILTimeContainer to update animations, the
elapsed time is calculated based on the client's currentTime().
That elapsed time is passed into updateAnimations and is used most of the
way "down".
In some cases during the update though, SMILTimeContainer::elapsed() i
11 matches
Mail list logo
