<br><br><div class="gmail_quote">2009/5/13 John Carlson <span dir="ltr"><<a href="mailto:john.carlson3@sbcglobal.net">john.carlson3@sbcglobal.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I understand that authoring tools keep a lot more stuff around and are more flexible for good reasons. Why can't a browser keep that same information around, perhaps hidden somewhere in the authoring application? I am referring to an authoring tool being an X3D/VRML application.</blockquote>
<div>I think it would be too hard to create a conventional authoring tool purely in vrml/x3d. For that you want to write it in a programming language - ie it would be specific to a browser developer's product line. Like Flux studio. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Why does making the browser smaller, lighter and less download seem to imply that an authoring application written in VRML/X3D must be smaller, lighter and less download? </blockquote><div>well you are right, if it is for authoring - for developers - then it does not need to be. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I understand that an authoring application written in C++ might be better performing, but it limits the authoring package to be written for a particular platform, whereas, if the authoring application were written in VRML/X3D, it should potentially be more portable.</blockquote>
<div>if it is written as a web application - where the hard work is done on the server, then this would be feasible.</div><div>Difficult thing here is that communications with server is not directly supported in portable fashion by the specification,</div>
<div>so there is one answer for you as to why not VRML/X3D.</div><div><br></div><div>i could still manage it using http and a couple of SAI calls that were not really designed for this (a robust networked app) [<a href="http://portal.acm.org/citation.cfm?id=1187337">http://portal.acm.org/citation.cfm?id=1187337</a> ] and you could do it with Ajax perhaps with less responsiveness (but that may not be a biggy in this kind of interactive app).</div>
<div><br></div><div>chris</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
Making the authoring package separate from the browser seems to mean that you don't get the same fidelity between the authoring tool and the browser (which is probably intentional--but the poor designer who just wants to get something perfect is left out).<br>
<br>
Routes are important, see:<br>
<br>
<a href="http://vpri.org/html/work/ifnct.htm" target="_blank">http://vpri.org/html/work/ifnct.htm</a><br><font color="#888888">
<br>
John</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
X3D-Public mailing list<br>
<a href="mailto:X3D-Public@web3d.org" target="_blank">X3D-Public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.vrshed.com">http://www.vrshed.com</a><br>There be greater truth at the centre.<br><a href="http://www.floatingorigin.com">http://www.floatingorigin.com</a><br>
<br>Association of Virtual Worlds, <a href="http://associationofvirtualworlds.ning.com/">http://associationofvirtualworlds.ning.com/</a><br><br><br>