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

Re: [Public WebGL] using the same context with multiple canvases

On Sat, 10 Nov 2012, Chris Marrin wrote:
> Yes, putting this on Canvas would be more sane. My proposal was simply 
> trying to avoid changes outside WebGL.

(I would encourage us all to communicate so that our organisation into 
different working groups do not get exposed in the platform's design. This 
is a classic example of Conway's Law. Avoiding changes outside of one spec 
is not a good reason to design something. :-) )

> My one issue with this approach is that having getContext() fail after 
> setContext() is confusing. Really getContext() becomes a misnomer used 
> this way. It is really createContext() or something similar. But since 
> we can't change that, maybe we can create a new pair of calls:
> 	canvas.setRenderingContext(context);
> 	context = canvas.getRenderingContext();
> Then we could leave getContext() alone and use it for legacy purposes. 
> But I agree that, in this scenario, getContext should fail if you've 
> ever called setRenderingContext().

What's the use case for getRenderingContext()?

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

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:
unsubscribe public_webgl