Activity for x3d
-
Don Brutzman committed [r39847] on Code
regression tests for release 4.0.65.5
-
TODO fixed
-
additional detail in error diagnostic
-
fixed TODO
-
already present in datasets/nrrd subdirectory
-
data file for ShadedBrain.x3d
-
x3d.py production errors creating HAnim nodes in XML output
-
fix garbled identifier
-
meta reference, Spatial Journalism: NY Times Pushing the Limits of Gaussian Splatting for Spatial Storytelling
-
meta reference, Spatial Journalism: NY Times Field Guide to Gaussian Splatting
-
belated commit of earlier change
-
NetBeans v29 -> 30
-
note validation error
-
avoid inclusion of period characters . in DEF labels since they do not meet X3D NMTOKEN naming conventions and can break ROUTE statements in ClassicVRML encoding
-
avoid inclusion of period characters . in DEF labels since they do not meet X3D NMTOKEN naming conventions and can break ROUTE statements in ClassicVRML encoding
-
release date
-
improved description
-
new feature: get parentNode
-
See ticket 117 for related fix and release.
-
Don't print out default container field in x3d.py
-
Now fixed
-
Issue 1 and issue 2 now appear to be fixed. See attached output, note corrected order of child nodes under HAnimHumanoid as well as inclusion of non-default containerField values on USE nodes. Release 4.0.65.5 of updated x3d.py is now available at https://pypi.org/project/x3d https://www.web3d.org/x3d/stylesheets/python/python.html
-
release 4.0.65.5
-
release 4.0.65.5
-
release 4.0.65.5
-
today's date
-
release 4.0.65.5
-
release 4.0.65.5
-
check SFString.REGEX_PYTHON()
-
bump version number for new release 4.0.65.5
-
adjusted sort meta tags, keeping identifier near bottom
-
add reference to resolved ticket
-
Issue 1 and issue 2 now appear to be fixed. See attached output, note corrected order of child nodes under HAnimHumanoid as well as inclusion of non-default containerField values on USE nodes. Release of updated x3d.py is planned soon.
-
Issue 1 and issue 2 now appear to be fixed. See attached output, note corrected order of child nodes under HAnimHumanoid as well as non-default containerField values on USE nodes. Release of updated x3d.py is planned soon.
-
Issue 1 and issue 2 now appear to be fixed. See attached output, note corrected order of child nodes under HAnimHumanoid as well as non-default containerField values on USE nodes. Release of updated x3d.py is planned soon.
-
x3d.py production errors creating HAnim nodes in XML output
-
avoid NMTOKEN warning about - in DEF name
-
improved NMTOKEN diagnostic
-
avoid warning about - in DEF name
-
avoid warning about - in DEF name
-
NMTOKEN naming convention: _ only
-
add support for GaussianSplats node
-
add WorldInfo with model title
-
spell out acronym in comment
-
additional meta information
-
corrected directory references
-
add GaussianSplats component INCLUDE and extensibility
-
add meta information
-
SF/MFQuaternion unit tests
-
SF/MFQuaternion unit tests
-
fix hasChild() functionality, additional output corrections
-
TODO fix messages
-
fix hasChild() functionality, additional output corrections
-
fix hasChild() functionality, additional output corrections
-
successful completion of SF/MFNode tests, automatically generated to x3d.py
-
successful completion of SF/MFNode tests, automatically generated to x3d.py
-
successful completion of SF/MFNode tests, automatically generated to x3d.py
-
successful completion of SF/MFNode tests, from manual debugging
-
better handle SFNode field initialization
-
better handle SFNode field initialization
-
better handle SFNode field initialization
-
fix problems with repl recursion by avoiding None values and seletively using repl
-
fix problems with repl recursion by avoiding None values and seletively using repl
-
fix problems with repl recursion by avoiding None values and seletively using repl
-
John W Carlson posted a comment on ticket #103
Is XSD and DTD validation ready? I see setters in X3DLoaderDOM.java. Please comment here or respond to email. Thanks!
-
improved testing update
-
canonicalization c14n, presentation looks the same
-
original by Holger Seelig, original name Animated.x3d
-
sort MF/SFNode order for XML output
-
sort MF/SFNode order for XML output
-
keep track of _parentNode vice _parentNodeName
-
keep track of _parentNode vice _parentNodeName
-
keep track of _parentNode vice _parentNodeName
-
keep track of _parentNode vice _parentNodeName
-
adjusted naming convention for _parentNodeName and _containerField to indicate that only internal use is intended
-
adjusted naming convention for _parentNodeName and _containerField to indicate that only internal use is intended
-
fix containerField handling for XML output, better sorting of HAnimHumanoid children
-
reduced diagnostics
-
fix containerField handling for XML output, better sorting of HAnimHumanoid children
-
editorial
-
validate x3d.py after creating new version
-
add GaussianSplats node, (v4.1) RenderedTexture remove update field (previously renamed to updateInterval)
-
support SF/MFQuaternion types, sort HAnimHumanoid SF/MFNode fields
-
support SF/MFQuaternion types, sort HAnimHumanoid SF/MFNode fields
-
(v4.1) RenderedTexture remove update field (previously renamed to updateInterval)
-
(v4.1) RenderedTexture remove update field (previously renamed to updateInterval)
-
(v4.1) RenderedTexture remove update field (previously renamed to updateInterval)
-
editorial, gaussian splats
-
Alexander Hoffman posted a comment on ticket #117
Hi John and Don, Thank you for addressing this, I have been traveling so I'm just getting back to my x3d experiments. I will update to 4.1 for future projects and I'm happy to resolve the ticket on Github when you deem fit. It seems issue 1 is resolved. Claude walked through the x3d.py source (4.0.65.3) and pointed to an example. Take PhysicalMaterial's XML() serializer as an example — around line 70878 it does: if self.baseTexture: # output this SFNode result += self.baseTexture.XML(indentLevel=indentLevel+1,...
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves the XML-output issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability (rather than an incorrect configuration). b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to...
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves the XML-output issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability (rather than an incorrect configuration). b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to...
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves the XML-output issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability (rather than an incorrect configuration). b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to...
-
x3d.py production errors creating HAnim nodes in XML output
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves the XML-output issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability (rather than an incorrect configuration). b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to...
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves the XML-output issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability. b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to a given node, which is a design deficiency...
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves the XML-output issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability. b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to a given node, which is a design deficiency...
-
I have improved the sort of child nodes within HAnimHumanoid, which mostly solves issue 1. For issue 2, while looking at how to properly handle generating the containerField value, realized a. No containerField information is applied anywhere in x3d.py so this is a missing capability. b. Python objects have no way to find out whether they have a parent, and indeed may have multiple parents. Thus there is insufficient information available to a given node, which is a design deficiency in the current...
-
We are awaiting stabilization of JSON Schema specification by IETF working group before attempting to merge the varying different JSON schema dialects already in existence. We will only be testing valid X3D models in XML and JSON once that effort finally begins.
-
Thanks for careful error reporting. This problem has been corrected and fixes are committed to version control. I expect to be able to update the copies on web3d.org in a few days.
-
add types SFQuaternion MFQuaternion, additional debugging improvements
1 >
