[x3d-public] JSweet translation of X3DJSAIL to JavaScript: needspecific design goals first

[Joseph D Williams]

> develop test cases for x3d4 or HAnim, I will do that.  Thanks to Joe for pointing me there.

I can talk with you about hanim examples/tests most any time, 

Thanks and Best, 
Joe



From: John Carlson
Sent: Tuesday, March 24, 2020 7:23 PM
To: Don Brutzman
Cc: Andreas Plesch; Katie Unger; X3D Graphics public mailing list
Subject: Re: [x3d-public] JSweet translation of X3DJSAIL to JavaScript: needspecific design goals first

Perhaps I haven’t been clear.   I see my position @ Web3d as a tester,  thus I expect to collaborate with other stakeholders to create test cases or example behaviors we want the system to perform.

We have abundant XML that I can generate test cases from.   I’m not generating code out of the blue.   I have a goal of generating code out of the blue, but that’s a long term goal.   This would be done to do code coverage.

I accidentally fell into a library writer position when we got to python.

I added my JSONParser to the browsers because no one was doing it, and I needed a real environment to test in.

I don’t see anything wrong with generating different versions of HelloWorld.js.

I resign from library development.   If someone wants me to develop test cases for x3d4 or HAnim, I will do that.  Thanks to Joe for pointing me there.

As a tester, I build code that I assert will not work, or I check the XML to see if the scene is supposed to fail.

The test cases for node are currently failing big time, I know.   I know I use methods instead of array access.   That needs to be fixed.   There are properties in the SAI I haven’t really spotted in the X3DUOM, so perhaps I need to look harder.   I need to add route methods to my serializer.

John

On Tue, Mar 24, 2020 at 8:23 PM John Carlson <yottzumm at gmail.com> wrote:
Design goal:  add existing X3D ecmascript SAI to HTML5 (chrome) and node.js

I tend to work from examples rather than specifications.  Once we have our test cases, we can start coding the library, using “test driven development.”  or “behavior driven development.”

We will build an npm environment, probably using webpack and yarn, and a suitable test framework.   Then I will start coding tests using  the test framework.   I believe we can use phantomjs or similar to run test cases in.

I will look for the Transform example.

Good news is I’m saving enough money on “shelter in place “ to afford a Web3d membership.

John

On Tue, Mar 24, 2020 at 7:44 PM Don Brutzman <brutzman at nps.edu> wrote:
On 3/24/2020 3:48 PM, John Carlson wrote:
> It seems like you have issues with the “generate first” approach. [...]

Yes.  Don't do that.  Don't even bother thinking about that.

Please look again at what I wrote.  You need specific design goals first.

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200324/946e7e6b/attachment.html>