[X3D-Public] X3D MultiTexturing - how about we start fixing thespec? :)

[Joe D Williams]

> WebGL is an OpenGL for JavaScript. It allows directly using shader 
> (GLSL) code. As such, it's light-years above the X3D MultiTexturing 
> options, but also not so easy to use (imperative, GLSL etc.).

Yes, that is why X3D browser includes those shader nodes. I'm still 
hoping an orderly best practice approach to WebGL shader 
implementations will lead to consistent implementations of 
MultiTexture in the declarative (well this one is really a declared 
procedure in that all or some of the procedure is embedded in the 
declarative form) X3D user code which I think is obvious and vital 
need for responsive HAnim.

http://www.khronos.org/registry/webgl/specs/latest/#6.25

If somebody that is in on the original definitions of VRML and X3D 
MultiTexture stuffs is also very involved in technical details and 
application aspects of WebGL then? hmmm ...

" - under your control."

http://www.amazon.com/dp/144932357X

Best Regards,
Joe

----- Original Message ----- 
From: "Michalis Kamburelis" <michalis.kambi at gmail.com>
To: "Joe D Williams" <joedwil at earthlink.net>
Cc: "x3d-public" <x3d-public at web3d.org>
Sent: Tuesday, August 06, 2013 11:43 AM
Subject: Re: [X3D-Public] X3D MultiTexturing - how about we start 
fixing thespec? :)


>> The only way you get to talk to the specmaster around here is to 
>> submit your
>> findings as bugs against the spec as entered using the Web3D.org 
>> Spec
>> comment form.
>> That is the only way to work with spec bugs in the ISO process.
>
> I did submit the multi-texturing bugs as spec comments at least two
> times already, without any response... I understand that these 
> issues
> are complicated and may require some discussion, that's why this 
> time
> I want to encourage some public talk, and would appreciate some
> confirmation like "Ok, the fix is applied to X3D spec in 
> development,
> move on" :)
>
> I don't mind submitting them another time as spec comments, if you
> think it is useful. But at this point, I'm not sure is it productive
> to duplicate existing reports.
>
>> Good Work on MultiTexture, it is needed for HAnim. Have you 
>> verified your
>> thoughts by looking at what WebGL does?
>
> WebGL is an OpenGL for JavaScript. It allows directly using shader
> (GLSL) code. As such, it's light-years above the X3D MultiTexturing
> options, but also not so easy to use (imperative, GLSL etc.).
>
> Michalis