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

Re: [Public WebGL] Feedback from HTML5 WG on WebGL | [Fwd: Re: WebGL | The 3D Canvas Context for HTML]



We certainly do want to begin discussions with other working groups to
see how the new array-like types might be repurposed. I am sure that
some extensions to their APIs will be necessary to fit uses like file
I/O. I hope we can achieve a good balance between functionality and
simplicity of the API; similar APIs which were developed for Java
ended up being both too complicated and difficult to optimize.

-Ken

On Fri, Dec 11, 2009 at 2:27 PM, Arun Ranganathan <arun@mozilla.com> wrote:
> Since our release yesterday, we've got some feedback from the W3C HTML5
> Listserv.  Most of the WHATWG post on the HTML5 listserv at W3C, which has
> the advantage of attracting Microsoft participation.  The W3C HTML5 listserv
> is archived publicly here: http://lists.w3.org/Archives/Public/public-html/
>
> On Thu, 10 Dec 2009 23:47:07 +0100, Arun Ranganathan <arun@mozilla.com>
> wrote:
>>
>> [...]
>
> I've been trying to cut my mailing list subscriptions recently so hopefully
> someone can forward this as appropriate.
>
> https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html
>
> The draft appears to use outdated Web IDL syntax. It also uses features,
> e.g. NameDeleter that are controversial with TC39 so you may want to
> reconsider using those.
>
> It also seems that a bunch of the new objects introduced should really be
> part of ECMAScript instead. E.g. all the new typed array interfaces.
>
> Some of the typedefs are scoped to WebGLRenderingContext but are in fact
> used all over the place.
>
> Also, why is it WebGLRenderingContext and not CanvasRenderingContextWebGL
> which would be more consistent with the existing CanvasRenderingContext2D?
>
> It does not seem to be defined when the event defined at the end of the
> specification is actually dispatched. The name of the event is also not
> defined, just the interface it implements. Also, if more than one resource
> is lost, which one does "resource" return? And why do you need the context
> attribute? Isn't it already clear that the event is for the WebGL context?
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
>

-----------------------------------------------------------
You are currently subscribe to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email: