that concept, that's not going to be feasible
in the foreseeable future. Maybe in a few years, optimistically.
On Wed, 19 Jun 2013, Benoit Jacob wrote:
I'd like to question the usefulness of canvas.supportsContext. I tried to
think of an actual application use case for it, and couldn't find one
2013/7/31 Ian Hickson i...@hixie.ch
On Wed, 31 Jul 2013, Benoit Jacob wrote:
Ping --- I thought that there was sufficient agreement in this thread,
around the fact that supportsContext, as currently spec'd and currently
implementable, is a feature without a valid use case, that removing
. Besides, even if we wanted to do that, there would remain the
problem that that's impossible to spec in a precise and testable way.
For these reasons, I still think that supportsContext should be removed
from the spec.
Benoit
2013/6/19 Benoit Jacob jacob.benoi...@gmail.com
Dear list,
I'd
that, there would remain the
problem that that's impossible to spec in a precise and testable way.
For these reasons, I still think that supportsContext should be removed
from the spec.
Benoit
2013/6/19 Benoit Jacob jacob.benoi...@gmail.com
Dear list,
I'd like to question the usefulness
Has the Canvas 2D community considered a WebGL-like model to the
introduction of additional features?
By the WebGL model, I mean:
- Define a core feature set that's conservative and limited, but
consistently implemented by all browsers. Enforce consistent support for it
by an exhaustive
2013/6/21 Benoit Jacob jacob.benoi...@gmail.com
Any other application use cases?
Anyone?
I believe that if no unquestionable application use case can be given, then
this function should be removed from the spec.
Benoit
for this particular feature is less
valuable than elsewhere.
Any other application use cases?
Keep in mind that this is all in sharp contrast with every single other
canvas / 2d / webgl API feature that I can think of, for which application
use cases are abundant.
Benoit
2013/6/19 Benoit Jacob jacob.benoi
Dear list,
I'd like to question the usefulness of canvas.supportsContext. I tried to
think of an actual application use case for it, and couldn't find one. It
also doesn't seem like any valid application use case was given on this
list when this topic was discussed around September 2012.
The
2013/6/19 Tab Atkins Jr. jackalm...@gmail.com
On Wed, Jun 19, 2013 at 11:17 AM, Benoit Jacob jacob.benoi...@gmail.com
wrote:
So let's look at the naive application usage pattern for supportsContext:
if (canvas.supportsContext(webgl)) {
context = canvas.getContext(webgl
2013/6/19 Boris Zbarsky bzbar...@mit.edu
On 6/19/13 3:34 PM, Tab Atkins Jr. wrote:
This is missing the point. You don't want to wait until it's actually
time to create the context. Unless you torture your code flow, by the
time you're creating a context you should already know that the
2013/6/19 Kenneth Russell k...@google.com
In my experience, in Chromium, creation of the underlying OpenGL
context for a WebGLRenderingContext almost never fails in isolation.
Instead, more general failures happen such as the GPU process failing
to boot, or creation of all OpenGL contexts
- Original Message -
On Tue, Sep 4, 2012 at 10:15 AM, Boris Zbarsky bzbar...@mit.edu
wrote:
So now our list is:
1) Have a way for pages to opt in to software rendering.
2) Opt canvases in to software rendering via some sort of
heuristic
(e.g. software by default until
- Original Message -
On Mon, 03 Sep 2012 00:14:49 +0200, Benoit Jacob bja...@mozilla.com
wrote:
- Original Message -
On Sun, 2 Sep 2012, Erik Möller wrote:
As we hardware accelerate the rendering of , not just with
the webgl
context, we have to figure out how
- Original Message -
What is really meant here by Canvas GPU acceleration?
This means use GL/D3D to implement the 2D canvas drawing primitives; but what
really matters here, is that this requires using a GL/D3D texture/surface as
the primary storage for the 2D canvas drawing buffer.
- Original Message -
On Sun, 2 Sep 2012, Erik Möller wrote:
As we hardware accelerate the rendering of , not just with
the webgl
context, we have to figure out how to best handle the fact that
GPUs loose the
rendering context for various reasons. Reasons for loosing the
- Original Message -
Sorry for joining the conversation late.
On Mar 28, 2012, at 1:39 PM, Kenneth Russell wrote:
On Wed, Mar 28, 2012 at 12:34 PM, Benoit Jacob bja...@mozilla.com
wrote:
1. In webgl.bufferData implementation, don't call glBufferData,
instead just cache
Before I joined this mailign list, Boris Zbarsky wrote:
C) Try to guess based on where the array buffer came from and have
different behavior for different array buffers. With enough luck (or
good enough heuristics), would make at least some WebGL work, while also
making non-WebGL things
17 matches
Mail list logo
