[x3d-public] X3DJSAIL ComposedShader

[Don Brutzman]

Roy and I have looked at it, indeed you appear correct that there is a ComposedShader gap in DTD/schema regarding fields which in turn impacts these other capabilities.

As it so happens, the content model for field/IS/CDATA is the most complex in the XML validations.  Have to wait until possible to really focus on the fix, can't afford to break Script validation in the meanwhile.

Recommend no workaround efforts, it will be better to wait for proper resolution correction and testing.  Sorry for the issue, thanks once again for patience on this.


On 2/21/2017 7:54 PM, yottzumm at gmail.com wrote:
> Or are you saying I should move my fields into the ShaderPart?
>
>
>
> John
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
>
>
> *From: *yottzumm at gmail.com <mailto:yottzumm at gmail.com>
> *Sent: *Tuesday, February 21, 2017 9:10 PM
> *To: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>; Don Brutzman <mailto:brutzman at nps.edu>; Roy Walmsley <mailto:roy.walmsley at ntlworld.com>
> *Subject: *X3DJSAIL ComposedShader
>
>
>
> I could be wrong, but I’m fairly sure that ComposedShader should produce the same code that ShaderProgram and ShaderPart produced in  CreateX3dSceneAccessInterfaceJava.xslt.  At least with respect to Fields.
>
>
>
> We’ve been over this before, but I’m taking a different tack.
>
>
>
> John
>
>
>
>
>


all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman