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

Re: [Public WebGL] WebGL NPOT texture support

Oops, this time to the whole list. Sorry, Ashley, for the spam.

Why would you need multiple shaders? The rect could be encoded in uniforms or even vertex attributes. I think you should look into atlasing because it might be a good idea for performance.

That all being said, I do support this as an extension since it is basically impossible to do correctly without it, but I'm hoping there are things you can try that let you move ahead without depending on such a long-lead process.

To the standards-minded folk: considering that WebGL has plenty of other ways a "bad first experience" might happen, something like NPOT textures that has semi-reasonable fallbacks (blurry images via rescaling is better than utter failure) would not be very high on my list. And if developers are the ones having that "bad first experience" then you'll never even have the user problem.


On Thu, Nov 17, 2011 at 4:48 PM, Benoit Jacob <bjacob@mozilla.com> wrote:

On 17/11/11 03:10 PM, Chris Marrin wrote:
And from the standpoint of an implementor of both desktop and mobile
WebGL, and someone interested in wide WebGL adoption, I think it's a
big mistake to push the limits of graphics capabilities at this
point. At this stage of WebGL's development I think ubiquity is more
important than power. If we get ourselves into a situation where
there are extensions not widely supported in hardware, we're going to
see fragmentation in content. Many people's first experience with
WebGL will be a bad one. There will come a time where it will be
appropriate to push the boundaries, but I don't think now is that

I sure do sympathize with this viewpoint, which I've repeatedly expressed myself in the past; for the other side of the argument, see my previous email.

I'm torn, and looking at the emails in this thread, it's a 50%-50% split. We need to find a way forward, that doesn't involve telling half of people here that they're wrong.

I'm thinking that we already did one very good thing by designing WebGL extensions in such a way that they're a lot harder to accidentally rely on, than OpenGL extensions. I'd like to see what more we can do in this direction.


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