<html><head></head><body>Oy! If you can't trust your tools, ...<br>
Oy-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br><br><div class="gmail_quote">Russ Kinter <pyth7@verizon.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif"><br />Funny, this whole topic is really been-there-damage-done, but it should be<br />pointed out that vizx3d studio needed cleaned up too.<br />Read the following fun thread from 2004: <br /><br /><a href="http://www.web3d.org/x3d/publiclists/vrml_list_archives/0404/msg00011.html">http://www.web3d.org/x3d/publiclists/vrml_list_archives/0404/msg00011.html</a><br /><br />It did lead to Vizx3d to be fixed so its VRML 2.0 output would not contain<br />exposedFields in Script Nodes. <br /><br />Russ Kinter<br /><br /><br />> -----Original Message-----<br />> From: x3d-public-bounces@web3d.org [mailto:x3d-public-bounces@web3d.org]<br />> On Behalf Of Dave A<br />> Sent: Monday, June 06, 2011 2:17 PM<br />> To: John Stewart<br />> Cc: x3d-public@web3d.org list<br />> Subject: Re: [X3D-Public] pseudo-related - was Re: Historical question<br />> <br />> Thanks Jon. I'm all for
cleaning up the generators. Too bad Vivaty<br />> Studio is off.<br />> It's hard to find the 'least common denominator' that would run on all<br />> platforms without<br />> having the entire spec in-brain.<br />> <br />> On 6/6/2011 11:10 AM, John Stewart wrote:<br />> > Dave;<br />> ><br />> > reading between the lines; some background:<br />> ><br />> > 1) FreeWRL used to be very "accepting" of syntax.<br />> ><br />> > 2) Some people complained that "invalid syntax" ran in FreeWRL; (see<br />> note below)<br />> ><br />> > 3) some tightening up of spec compliance has occurred. In particular, if<br />> you invoke "strict" parsing, (eg, command line "freex3d", if it is built<br />> for your platform) will check each node and each field against specified<br />> profiles.<br />> ><br />> > The note above; I can really understand people wanting the browsers to<br />> correctly
implement the spec, and only the spec. On the other hand, the<br />> generators should respect the spec, the viewers should render what it can,<br />> even if it is not totally 100% correct.<br />> ><br />> > (it has been a few years since I wrote the tightening via the "freex3d"<br />> invocation method; have not looked at this part of the code in a long<br />> time; I assume it still works)<br />> ><br />> > Thanks for the interesting discussion.<br />> ><br />> ><br />> > JohnS.<br />> ><br />> ><br />> ><br />> > -----<br />> > No virus found in this message.<br />> > Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br />> > Version: 10.0.1382 / Virus Database: 1511/3680 - Release Date: 06/04/11<br />> ><br />> ><br />> ><br />> <br />><hr /><br />> X3D-Public mailing list<br />> X3D-Public@web3d.org<br />> <a
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br /><br /></pre></blockquote></div></body></html>