[x3d-public] List of X3D problems or missing features, from the point of view of Michalis and Castle Game Engine

[GPU Group]

PUBLIC DOMAIN IDEAS >>>
OK. Any hypotheses for the remaining issues holdup / slow progress?
-Doug
more..
H0: general committee capacity / not enough committees or committee members
H1: need to rotate in committee members who are interested in specific
issues, to drive them over the finish line
H2: unsolvable problems specific to each issue
Example: For blending, what would the x3d syntax look like if I want no
blending? Or 50/50?
One problem: how to make the old fashioned no-blend the default. Lets give
that design principle a name. How about New Defaults Preserve Old Ways.
How about
Material {
SFFloat blendWithTexture 0 [0-1]
}
with 1 meaning "use material, except for texture transparency, if/when
texture loads." and 0 meaning texture over-rides material 100% - the old
way.

Or do you have the syntax and semantics worked out already? If so what does
it look like? And does it meet all design principles stated by web3d.org on
their design principles page?
H3: web3d is missing a design principles page, leading to long decision
making processes.

<<PUBLIC DOMAIN IDEAS

On Sun, Mar 4, 2018 at 11:25 AM, Michalis Kamburelis <
michalis.kambi at gmail.com> wrote:

>  2018-03-04 15:49 GMT+01:00 GPU Group <gpugroup at gmail.com>:
> > Michalis,
> > Thanks again for sharing your compositing shaders techniques with freewrl
> > project.
> > And I crave a web3d-legal way to do blend mode (material x texture).
> > -Doug
> > I suspect these ideas would need to be submitted through web3d specs
> > comments form -whereby you sign away claims / ownership- to ever make it
> > into the future specs, unless specs committee stumbles onto the same
> ideas
> > independently.
> > http://www.web3d.org/content/web3d-standards-comment-form
> >
>
> As for legal stuff: I hereby release any rights to the ideas and prose
> on https://github.com/michaliskambi/x3d-tests/wiki . Consider it all
> public domain. I added appropriate note to the bottom
> of https://github.com/michaliskambi/x3d-tests/wiki .
>
> As for spec comments -- some of my issues are already submitted. I
> think I submitted the multi-texturing problems at least 3 times as
> spec comments :) Quotes/backslashes clarifications are also submitted
> (by me, and others as well, as I heard).
>
> In practice, posting about them on this list caused more progress --
> we had discussions and consensus about fixing them on x3d-public and
> teleconference, which was good. For some issues, I also see the
> understandable need to discuss about them first in the open. So this
> open mailing list seems more suitable as a "first place for
> discussion" :)
>
> Regards,
> Michalis
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180304/9b7d87ff/attachment.html>