[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Public WebGL] Is section 6.3 still needed ? (was: New Rendering Pipeline ?)
- To: public webgl <email@example.com>
- Subject: [Public WebGL] Is section 6.3 still needed ? (was: New Rendering Pipeline ?)
- From: Cedric Vivier <firstname.lastname@example.org>
- Date: Sat, 28 Aug 2010 13:28:25 +0800
- Cc: "Gregg Tavares (wrk)" <email@example.com>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=hSdTK9GdkawDoLfPyWi7l1lsrb5Ap8nOH3J6D9q/RSI=; b=VgMvaKwkKi1y2d+959MJSTPZ5pC6K7Tsrq6OusjxP95PsnmYllqSAhwZ9mpIr/T7fO znTRE5bS7msIoYhPGGxle3bD6iz4/hLV8ZN8w2znWSCKJ9EqOGpjdhqEl+ZUX2+zJxYs N59Ra6RyW6DTWIUwFrZnffMDrZCJ2udzGBUqY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; b=b+xvhTEPsebJqNG+lY+SveV/T2/oM0Ake253TIL52NgtwuQC2P8cqLhLnyvXi6Q9li VbQXgMtlwhB5VYuF4S5K8wE+BHW5z8b7hjcGXU5BvEU/OYuoIShLqMaUdk0wOhFnAB8o gDCgBEB7YIC0hsSH8wF0FW+2lF1ff3ZOtL1iw=
- Sender: firstname.lastname@example.org
On Wed, Aug 25, 2010 at 12:00, Cedric Vivier <email@example.com>
Of course if NaCl on Windows Chrome is _not_ supposed to ever run on top of Direct3D/Angle then my question is moot and I apologize for the being a bit off-topic.
With the news of Chrome jumping into the GPU-accelerated HTML compositing train as well, I stumbled upon an interesting document about how Chrome handles accelerated compositing, WebGL content and NaCl 3D rendering within the same "GPU process" :
After reading this article (and glancing at the code) I'm still very curious how NaCl can be fully ES 2.0 conformant with no restriction similar to WebGL spec section 6.3 when running on top of OpenGL desktop and Direct3D/ANGLE.
Has a solution to reliably emulate the ES 2.0 semantics been developed somehow ?
If so, assuming the same trick can be done on any WebGL implementation, do we still need to keep section 6.3 (and the divergence from ES 2.0 it brings) ?