<DIV><BR><BR>----- Original Message -----<BR>From: Joe D Williams <joedwil@earthlink.net><BR>Date: Monday, February 1, 2010 10:20 pm<BR>Subject: Re: [X3D-Public] Open-Source Multi-User<BR>To: JOHN COADY <johncoady@shaw.ca>, Don Brutzman <brutzman@nps.edu><BR>Cc: x3d-public@web3d.org<BR><BR>> HI John,<BR>> <BR>> Good work and a lot of work.<BR>> I wish I had seen this back then.<BR>> <BR>> Why do we have to do this?<BR>> <BR>> tmpScene = browser.createX3DFromString(s1);<BR>> nodes = tmpScene.getRootNodes();<BR>> scene = browser.getExecutionContext();<BR>> // Nodes must be removed before adding to another scene<BR>> for(j=0; j < nodes.length; j++) {<BR>> tmpScene.removeRootNode(nodes[j]);<BR>> scene.addRootNode(nodes[j]);<BR>> <BR>> That is, why remove the root node from tmpScene before adding it <BR>> to <BR>> scene?<BR>> <BR>> Tony had described this in AjaX3D code and elsewhere as:<BR>> "// Do a bit of work to deal with the quirky X3D add/remove root <BR>> node <BR>> paradigm"<BR>> I never have understood that.<BR>> </DIV>
<DIV> </DIV>
<DIV>I don't know the reason for it but I took it from example B.3 Create Nodes from Annex B in the ECMAScript spec.</DIV>
<DIV> </DIV>
<DIV><A href="http://web3d.org/x3d/specifications/ISO-IEC-19777-1-X3DLanguageBindings-ECMAScript/">http://web3d.org/x3d/specifications/ISO-IEC-19777-1-X3DLanguageBindings-ECMAScript/</A></DIV>
<DIV> </DIV>
<DIV><BR>> When we have this:<BR>> <BR>> scene = browser.getExecutionContext();<BR>> <BR>> then why not scene.getNamedNode() and replace fields directly, <BR>> or <BR>> add/replace Children? Do I have to deal directly with root nodes?<BR>> </DIV>
<DIV> </DIV>
<DIV> I use scene = browser.getExecutionContext(); in function B7 when I was testing adding a new node to an existing scene.</DIV>
<DIV> </DIV>
<DIV> I used getNamedNode in function B8 when I wanted to modify an existing node in a scene which has known DEF value.</DIV>
<DIV> </DIV>
<DIV>The FLUX browser used a function called getNode to get a named node but this didn't work on Octaga browser. The getNamedNode worked on Octaga but not on FLUX. I'm not sure which one is supposed to be used according to the spec. That is why the code for function B8 handles these cases differently.</DIV>
<DIV><BR>> Did these run well then? I can't get them loaded in any html <BR>> browser <BR>> now but will try some more. Actually the code doesn't look that <BR>> much <BR>> different between Flux and Octaga. Ever any comparison with BSContact?</DIV>
<DIV> </DIV>
<DIV> Yes these ran well, however function B7 did not work on the Octaga browser, only on the FLUX browser. I am using a windows XP machine with Internet Explorer. I never tried BSContact but you I suppose you can try it out for yourself and try adding BSContact plugin and have all 3 browsers running in the same web page and see if they behave the same way.</DIV>
<DIV><BR>> <BR>> Any other X3D browser makers want to get some examples similar <BR>> to <BR>> these?<BR>> <BR>> Thanks and Best Regards, '<BR>> Joe<BR>> www.hypermultimedia.com/ajax3d/<BR>> 2006,2007<BR>> <BR>> ----- Original Message ----- <BR>> From: "JOHN COADY" <johncoady@shaw.ca><BR>> To: "Don Brutzman" <brutzman@nps.edu><BR>> Cc: <x3d-public@web3d.org><BR>> Sent: Monday, February 01, 2010 2:17 PM<BR>> Subject: Re: [X3D-Public] Open-Source Multi-User<BR>> <BR>> <BR>> > Hi<BR>> ><BR>> > A few years ago I put together a website to <BR>> compare External SAI <BR>> > between Octaga and FLUX players. I put the 2 players side by <BR>> side on <BR>> > a webpage and then created a number of buttons to perform some <BR>> > External SAI functionality and see how the two browsers <BR>> compared in <BR>> > handling the SAI commands. The website is<BR>> ><BR>> > http://members.shaw.ca/johncoady/SAICompare.html<BR>> ><BR>> > By clicking on the buttons at the top of the page, the same <BR>> content <BR>> > should show up in both browsers. However, I found that there <BR>> were <BR>> > some differences in behaviour for a couple of the buttons. You <BR>> can <BR>> > view the SAI source code for each of the tests by performing a <BR>> > view -> source in your HTML browser when the above web page is <BR>> > loaded. At the time I created the website the browsers would <BR>> load <BR>> > automatically if they were not present on your system, however <BR>> I <BR>> > think that the FLUX browser has moved to Vivaty and may not <BR>> load <BR>> > automatically anymore.<BR>> ><BR>> > Regards<BR>> ><BR>> > John Coady<BR>> ><BR>> > ----- Original Message -----<BR>> > From: Don Brutzman <brutzman@nps.edu><BR>> > Date: Monday, February 1, 2010 9:53 am<BR>> > Subject: Re: [X3D-Public] Open-Source Multi-User<BR>> > To: Russ Kinter <pyth7@verizon.net><BR>> > Cc: X3D Graphics public mailing list <x3d-public@web3d.org><BR>> ><BR>> >> Russ, thanks for the exciting "heads up" about this development.<BR>> >><BR>> >> As you may have notices, we are working on good exemplar scenes<BR>> >> that demonstrate proper use of external SAI with HTML using <BR>> >> Javascript<BR>> >> or Java. Surprisingly we've found very few common<BR>> >> examples. I hope<BR>> >> that this team can please consider releasing some advance<BR>> >> examples to<BR>> >> the X3D Working group (or publicly if you prefer) so that we <BR>> can <BR>> >> work<BR>> >> towards consistent definition of best practices. POCs are<BR>> >> Joe Williams<BR>> >> with John Stewart, Johannes Behr and myself tracking this challenge<BR>> >> during our weekly HTML5-X3D teleconferences. TIA, good<BR>> >> luck with your<BR>> >> work.<BR>> >><BR>> >> all the best, Don<BR>> >> -- <BR>> >> Don Brutzman Naval Postgraduate School, Code<BR>> >> <BR>> USW/Br brutzman@nps.edu<BR>> >> Watkins 270 MOVES Institute, Monterey CA 93943-5000<BR>> >> USA work +1.831.656.2149<BR>> >> X3D, virtual worlds, underwater robots, XMSF<BR>> >> http://web.nps.navy.mil/~brutzman<BR>> >> _______________________________________________<BR>> >> X3D-Public mailing list<BR>> >> X3D-Public@web3d.org<BR>> >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org<BR>> >><BR>> ><BR>> <BR>> <BR>> -----------------------------------------------------------------<BR>> ---------------<BR>> <BR>> <BR>> > _______________________________________________<BR>> > X3D-Public mailing list<BR>> > X3D-Public@web3d.org<BR>> > http://web3d.org/mailman/listinfo/x3d-public_web3d.org<BR>> > <BR>> <BR>> </DIV>