[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] IE 11

It seems to me like the most effective thing at the moment may be to try and mobilize WebGL developers to contact Microsoft with real-world apps/demos that indicate a need for API "X". I'd imagine that if enough developers wrote in eventually the entire API would worm it's way onto Microsoft's "priority" list.

And, if after all that some APIs just don't see much or any demand, it's honestly probably not a crisis is MS excludes them. I'm all for supporting the standard as is, but there is something to be said for not spending resources supporting a function call only 3 developers have ever tried.


On Wed, Jul 31, 2013 at 10:26 AM, Ben Vanik <benvanik@google.com> wrote:
(opinions are my own, not my employers)

What IE is shipping should be called 'WebGL Lite', if they are not going to be implementing the full spec.

Had they wanted to encourage the removal of these calls from the spec they should have participated earlier. Developers writing code will now have to worry about which features IE has arbitrarily chosen not to implement and as such will learn to avoid using them even though doing so may have been a perfectly sensible thing to do. It feels like a ham-fisted effort to force changes to the spec after it's been shipped without the involvement of Khronos and its members (who spent a great deal of effort making sure the spec was good) or the community.

Can anyone help the IE team see reason here? I feel like they are hurting their image in what could have been their moment of triumph :/

On Wed, Jul 31, 2013 at 4:50 AM, Daniel Koch <dkoch@nvidia.com> wrote:
That seems kind of silly.  There already is an existence proof out there that all the WebGL features can be mapped to D3D9 and D3D11 fairly reasonably… (and it's even open source if they need help figuring it out).  Ah well, I suppose something is better than nothing?


Microsoft's message at the moment is that it's an early developer preview and they are actively working on implementing more functionality before launch. They have also stated that they do not intend to implement every WebGL API (They explicitly called out vertexAttrib[1234]f as an API they are planning to ignore as it doesn't map to D3D11 well), and are looking for developer feedback on which APIs should receive priority.


On Tue, Jul 30, 2013 at 5:19 PM, Mark Callow <callow.mark@artspark.co.jp> wrote:

I tried the IE 11 preview. The simple get.webgl.org cube works as does the slightly more complex one on khronos.org. However the WebGL aquarium does not. I get a cyan background and the menu but nothing else. I do not have time to investigate.



注意:この電子メールには、株式会社エイチアイの機密情報が含まれている場合が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情報の使用を固く禁じております。エラー、手違いでこのメールを受け取られましたら削除を行い配信者にご連絡をお願いいたし ます.

NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.