Re: [Public WebGL] New Rendering Pipeline ?

Subject: Re: [Public WebGL] New Rendering Pipeline ?

From: Vangelis Kokkevis <vangelis@google.com>

Date: Tue, 24 Aug 2010 11:44:13 -0700

Cc: public webgl <public_webgl@khronos.org>

Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1282675456; bh=rFz8kP6XuM9CtZqaZF/nmJdeAfs=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=jQ8ivBJs/w5P3JxQM6Yn8W1CK2Dn5w6HtYY6rUnjBIXe+wsz9zn4/5ftQonEuAH0C BveqKdWpzO2olcSVTv/MA==

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=riIMvKItmWkYhQgKIqUcoHXED9Jwcgf+VND8X3XTGkE=; b=aRoLtGmIhcgDcbyOc03AuDrHTXQlqK9ZIqK0bkC/inAGnJTZYwSY5iSQI8kp16v1Ea j/ZFkGzifgrSsYzMcjjA==

Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=eukX4uXyHhUe55+RoiaQO2Ajdf+mT0d7KV0Ts4PPyXT/JlO5/GaVeEScUZSjkzjOl1 VwbK7c0U2kAQjni/kT6Q==

In-reply-to: <C56464AF-3CB6-4D57-A36A-8F0FFD310799@apple.com>

References: <AANLkTi=4rDbHJPWMHqF=eBcyP+Cv1nxM2_=OTUvR4+ni@mail.gmail.com> <4C7247E9.5000805@sjbaker.org> <C56464AF-3CB6-4D57-A36A-8F0FFD310799@apple.com>

Sender: owner-public_webgl@khronos.org

On Tue, Aug 24, 2010 at 9:30 AM, Chris Marrin <cmarrin@apple.com> wrote:

On Aug 23, 2010, at 3:05 AM, Steve Baker wrote:

> WebGL is (essentially) built on top of either OpenGL, or OpenGL-ES - and
> behaves more or less exactly like OpenGL-ES.
>
> The rendering pipeline is therefore precisely the same as those graphics
> libraries. The only places where there are really any differences are
> at the API level:
>
> * Restrictions due to the fact we're running in a web browser (eg, for
> the moment, there are no OpenGL extensions).
> * Extensions to make things more convenient (eg the ability to load a
> texture from disk with a single command)
> * Things made necessary by the need to interface to _javascript_ rather
> than C/C++ (eg The Float32Array stuff).

There are also a small number of restrictions added to make it possible to use D3D as a backend for WebGL. I believe there was an intent to put such differences on the Wiki, similar to http://khronos.org/webgl/wiki/WebGL_and_OpenGL_Differences, but I don't see it.

They are in Section 6 of the WebGL spec, specifically 6.5 through 6.9 .

Vangelis

-----
~Chris
cmarrin@apple.com

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