[x3d-public] X3D meeting minutes 20 AUG 2021, C C++ C# and Mantis MetadataDate
John Carlson
yottzumm at gmail.com
Thu Aug 26 18:40:15 PDT 2021
Status, taking first integrating google drive (downloaded a while ago)
changes provided by Myeong into my GitHub coderextreme/X3D repository,
so we can start doing diffs as a group. GitHub was changed on Aug 18th
https://www.web3d.org/member-only/mantis/view.php?id=1371 (please update
description with below)
I have done some ```git rm -r ``` and ```git mv``` to remove WDs from my
local GitHub and move Google downloaded folders on top of WDs. If you
want to keep a copy of the old WD's let me know. I am ready to do a
```git commit```, and have done a ```git commit --dry-run``` below. I do
have Web3DConsortium/X3D repository checked out separately that is
up-to-date with Web3DConsortium/X3D (which was changed 14 days ago).
19777-{3,4,5} have changed 10-12 months ago on Web3DConsortium GitHub,
so I think it's time to update.
Once the 3 WD's are in my remote repository, we can start doing diffs
against the Web3D repository, but I don't know what to do with the
19777-6 currently not in the Web3DConsortium repository. I suggest
someone more knowledgeable about doing the pull requests start pulling
in changes from my repository once I've got them checked in.
I have done NOT git adds that I know of, merely ```git mv``` to move new
WDs into position.
Current branches are to be ccppcs and main locally. I don't really know
how to use branches, I guess.
Summary of changes (note that there appear to be problems with some images?)
$ git commit --dry-run
On branch ccppcs
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
renamed:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/images/cube.gif
->
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Images/cube.gif
renamed:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/images/x3d.png
->
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Images/x3d.png
renamed:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/images/x3dbar.png
->
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Images/x3dbar.png
deleted:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/VRMLrelationship.html
new file:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/WD.png
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/Web3D_LB.css
renamed:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/X3D_CPP.html
->
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/X3D_C.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/abstracts.html
deleted:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/compilation.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/concepts.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/concretes.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/examples.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/foreword.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/functions.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/glossary.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/introduction.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/references.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/running_header.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/scope.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/tables.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/Part03/types.html
modified:
ISO-IEC19777/ISO-IEC19777-3/ISO-IEC19777-3v3.3/ISO-IEC19777-3v3.3-WD/index.html
new file:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Images/IECLogo.gif
new file:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Images/ISOLogo.gif
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/images/cube.gif
->
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Images/cube.gif
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/images/x3d.png
->
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Images/x3d.png
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/images/x3dbar.png
->
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Images/x3dbar.png
new file:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/WD.png
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/Web3D_LB.css
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/X3D_CPP.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/abstracts.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/concepts.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/concretes.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/conformance.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/examples.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/foreword.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/functions.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/glossary.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/introduction.html
deleted:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/nodeInterfaces.html
deleted:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/nodeTypeInterfaces.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/references.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/running_header.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/scope.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/tables.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/Part04/types.html
modified:
ISO-IEC19777/ISO-IEC19777-4/ISO-IEC19777-4v3.3/ISO-IEC19777-4v3.3-WD/index.html
new file:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Images/IECLogo.gif
new file:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Images/ISOLogo.gif
new file:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Images/cube.gif
new file:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Images/x3d.png
new file:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Images/x3dbar.png
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample1.java
->
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample1.cs
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample2.java
->
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample2.cs
new file:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample3.cs
deleted:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample3.java
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample4.java
->
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample4.cs
renamed:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample5.java
->
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Examples/SAIExample5.cs
deleted:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/VRMLrelationship.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/Web3D_LB.css
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/X3D_CSharp.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/abstracts.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/concepts.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/concretes.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/examples.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/foreword.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/functions.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/glossary.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/introduction.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/references.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/running_header.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/scope.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/tables.html
modified:
ISO-IEC19777/ISO-IEC19777-5/ISO-IEC19777-5v3.3/ISO-IEC19777-5v3.3-WD/Part05/types.html
On 8/26/21 9:34 AM, Brutzman, Donald (Don) (CIV) wrote:
>
> Again: it would be useful to have to have a design page that discussed
> programming patterns and open issues.
>
> Again: GitHub is master version, being aware that differences exist
> but are not identified isn’t very useful.
>
> Again: Hoping we can “get on the good foot” in how this effort is
> pursued. This is how the Java, JSON, Python and Turtle language
> bindings built towards consensus and were all successfully accomplished.
>
> Thanks for all efforts, hopefully they can become productive and
> fruitful by working deliberately together.
>
> 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 <http://faculty.nps.edu/brutzman>
>
> *From: *John Carlson <mailto:yottzumm at gmail.com>
> *Sent: *Friday, August 20, 2021 12:36 PM
> *To: *Brutzman, Donald (Don) (CIV) <mailto:brutzman at nps.edu>;
> x3d-public at web3d.org <mailto:x3d-public at web3d.org>; Myeong Won Lee
> <mailto:myeongwonlee at gmail.com>; GPU Group <mailto:gpugroup at gmail.com>
> *Subject: *Re: [x3d-public] X3D meeting minutes 20 AUG 2021, C C++ C#
> and Mantis MetadataDate
>
> NPS WARNING: *external sender* verify before acting.
>
> Don, Myeong, Doug,
>
> I noticed that there are no virtual methods in the C++ spec SAI I got
> (examples, yes, except for ~SAIExample5()) on drive.google.com. I do
> not think they are necessary, but may be useful when defining
> subclasses for people who want to subclass from the SAI abstract and
> concrete nodes. https://www.geeksforgeeks.org/virtual-function-cpp/
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.geeksforgeeks.org%2Fvirtual-function-cpp%2F&data=04%7C01%7Cbrutzman%40nps.edu%7C4e6ee194cc544357635908d964118d12%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637650850010851004%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=EkRmxJLy9eZ1jjBqCZ%2FS99OiG9B9NcBGWff6ixidzNA%3D&reserved=0>
> Note that most methods are virtual in Java, without the keyword. I
> think virtual methods are slower than regular methods, last I heard.
> But I'm pretty sure all destructors should be virtual? I've
> forgotten. Some discussion whether destructors should be present in
> the spec is welcome. The virtual destructor ensures that the
> superclass destructor is not called.
>
> I think it would be useful to have Doug Sanden review the abstract and
> concrete class and structs before making big decisions.
>
> I am also unsure why the first parameter to many C function pointer
> declarations is void* instead of passing a pointer to a struct type?
>
> In all cases, C/C++/C# it might be useful for setter functions and
> members to return this or *this, instead of void. We need set
> functions to return this for creating builders I'm fairly sure. (In C
> SAI, the first parameter is called this, it's not a keyword that I
> know of).
>
> I'm glad I am reviewing this! We'll see if anything else pops into my
> head after I send the message!
>
> Thanks,
>
> John
>
> On 8/20/21 1:46 PM, Brutzman, Donald (Don) (CIV) wrote:
>
> Attendees John Carlson, Vince Marchetti, Dick Puk, Don Brutzman
>
> 1.Very useful discussion today, we reviewed proposed language bindings
>
> 1. 19755- 3, C
> 2. 19755- 4, C++
> 3. 19755- 5, C#
>
> We discussed whether special treatment is deserved for exposing
> these draft specifications. 22 Web3D members have access to them now.
>
> Language bindings need compilable interfaces for ISO, and at least
> two implementations for Web3D.
>
> Close inspection of each shows that a handful of example programs
> are available for test development, and could be used as basis for
> X3dToCCppCsharp.xslt conversion stylesheet.
>
> Close inspection of detailed abstract interfaces, and detailed
> node/statement implementations for libraries are available (with
> some omissions). Each appears quite similar to the others.
> Regeneration via X3DUOM of compilable “header” or interface files
> matching the source code in the HTML is possible.
>
> C and C++ language compilation is easily possible using gcc
> compiler. Compilation of C# is not so clear, some open-source
> implementations are available. Once initial compilation of
> headers is accomplished, further scrutiny and possible evolution
> of design patterns would be straightforward. We’ll use gcc on the
> next round since it is part of our build infrastructure already.
>
> 1. GCC, the GNU Compiler Collection https://gcc.gnu.org
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.gnu.org%2F&data=04%7C01%7Cbrutzman%40nps.edu%7C4e6ee194cc544357635908d964118d12%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637650850010860960%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=InQmxP%2BpSNqMvgzuLehZ1WsMAhVzTsElQ6bPWfUJeqw%3D&reserved=0>
>
> 2. https://stackoverflow.com/questions/26078437/why-does-gcc-support-java-and-not-c-sharp
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F26078437%2Fwhy-does-gcc-support-java-and-not-c-sharp&data=04%7C01%7Cbrutzman%40nps.edu%7C4e6ee194cc544357635908d964118d12%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637650850010860960%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ID4Gzh%2Bw9bW80EYdfPZCPLjH1m%2BlKDZnZGINmJjcyHA%3D&reserved=0>
>
>
> We have enough that immediate sharing of shared specifications can
> be deferred until broader discussion is warranted. Sharing of
> generated code will help, and that does not have to be restricted.
>
> We are concerned about personnel availability, but will keep
> working on it step by step.
>
>
> We will welcome all help and participation as the work proceeds.
>
> 2.Mantis issue progress is persevering steadily each week.
>
> 1.Mantis 1218 for creating a MetadataDate or MetadataTime node
> needs to be deferred to X3D4.1. Meanwhile we might an example
> scene demonstrating how to do such representations with existing
> nodes, workably across all forms of X3D. E.g. pseudocode examples:
>
> <MetadataDouble name=”time” value=“0.0”
> reference=”Unix reference of time with start at 1 JAN 1970”/>
>
> <MetadataString name=”TuesdayLunch”
> value=“24-AUG-2021-1200-pacific” reference=”XSD, XML Schema
> Definition”/> <MetadataString name=”ThankGoodnessItsMonday”
> value=“23-AUG-2021-1200-pacific” reference=”ISO 8601 Time standard”/>
>
> Any scene of examples would be fully detailed and cross-referenced
> for clarity.
>
> Mantis 1218: 07.2.4 MetadataDate - New node type, or new data type
>
> https://www.web3d.org/member-only/mantis/view.php?id=1218
> <https://www.web3d.org/member-only/mantis/view.php?id=1218>
>
> 2.Other mantis issues are being fixed and addresses each week.
> Membership has value.
>
> https://www.web3d.org/member-only/mantis/view_all_bug_page.php
> <https://www.web3d.org/member-only/mantis/view_all_bug_page.php>
>
> Thanks everyone for a worthy effort today. Have fun with X3D! 8)
>
> *From:* Brutzman, Donald (Don) (CIV)
> *Sent:* Friday, August 20, 2021 12:27 AM
> *To:* x3d-public at web3d.org <mailto:x3d-public at web3d.org>
> *Cc:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> <mailto:brutzman at nps.edu>
> *Subject:* X3D meeting agenda 20 AUG 2021, C C++ C# and Mantis
>
> Regular weekly call once again this week, Friday 10-1100 Pacific
> on Web3D conference line.
>
> We will review our approach to C C++ C# encodings and also ongoing
> Mantis progress. Additional topics welcome.
>
> all the best, Don
>
> --
>
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu <mailto: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 <http://faculty.nps.edu/brutzman>
>
>
>
> _______________________________________________
>
> x3d-public mailing list
>
> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org <http://web3d.org/mailman/listinfo/x3d-public_web3d.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210826/e0937f02/attachment-0001.html>
More information about the x3d-public
mailing list