You can subscribe to this list here.
2011 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(9) |
Jun
(23) |
Jul
(9) |
Aug
(29) |
Sep
(5) |
Oct
(24) |
Nov
(31) |
Dec
(19) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2012 |
Jan
(18) |
Feb
(17) |
Mar
(43) |
Apr
(38) |
May
(21) |
Jun
(51) |
Jul
(27) |
Aug
(12) |
Sep
(24) |
Oct
(19) |
Nov
(45) |
Dec
(21) |
2013 |
Jan
(59) |
Feb
(64) |
Mar
(63) |
Apr
(59) |
May
(74) |
Jun
(28) |
Jul
(28) |
Aug
(19) |
Sep
(26) |
Oct
(65) |
Nov
(24) |
Dec
(23) |
2014 |
Jan
(62) |
Feb
(34) |
Mar
(18) |
Apr
(24) |
May
(18) |
Jun
(21) |
Jul
(53) |
Aug
(22) |
Sep
(31) |
Oct
(22) |
Nov
(23) |
Dec
(30) |
2015 |
Jan
(29) |
Feb
(62) |
Mar
(58) |
Apr
(68) |
May
(53) |
Jun
(17) |
Jul
(17) |
Aug
(35) |
Sep
(88) |
Oct
(17) |
Nov
(71) |
Dec
(55) |
2016 |
Jan
(76) |
Feb
(105) |
Mar
(69) |
Apr
(31) |
May
(24) |
Jun
(26) |
Jul
(23) |
Aug
(42) |
Sep
(17) |
Oct
(31) |
Nov
(17) |
Dec
(10) |
2017 |
Jan
(13) |
Feb
(42) |
Mar
(19) |
Apr
(20) |
May
(90) |
Jun
(23) |
Jul
(38) |
Aug
(38) |
Sep
(8) |
Oct
|
Nov
(16) |
Dec
(11) |
2018 |
Jan
(3) |
Feb
(1) |
Mar
(38) |
Apr
(19) |
May
(117) |
Jun
(12) |
Jul
(27) |
Aug
(41) |
Sep
(8) |
Oct
(3) |
Nov
(2) |
Dec
(1) |
2019 |
Jan
(3) |
Feb
(16) |
Mar
(57) |
Apr
(13) |
May
(33) |
Jun
(11) |
Jul
(14) |
Aug
(2) |
Sep
(22) |
Oct
(6) |
Nov
(29) |
Dec
(11) |
2020 |
Jan
(43) |
Feb
(4) |
Mar
(2) |
Apr
(9) |
May
(63) |
Jun
(22) |
Jul
(30) |
Aug
(8) |
Sep
(14) |
Oct
(28) |
Nov
(10) |
Dec
(17) |
2021 |
Jan
(25) |
Feb
(6) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(32) |
Jul
(13) |
Aug
|
Sep
(32) |
Oct
|
Nov
(11) |
Dec
(38) |
2022 |
Jan
(26) |
Feb
(4) |
Mar
|
Apr
(18) |
May
(21) |
Jun
(22) |
Jul
(7) |
Aug
|
Sep
|
Oct
(3) |
Nov
(9) |
Dec
|
2023 |
Jan
(35) |
Feb
(63) |
Mar
(2) |
Apr
(19) |
May
(5) |
Jun
(9) |
Jul
|
Aug
(11) |
Sep
(19) |
Oct
(9) |
Nov
(4) |
Dec
|
2024 |
Jan
(4) |
Feb
(6) |
Mar
|
Apr
(5) |
May
(3) |
Jun
(1) |
Jul
(7) |
Aug
(6) |
Sep
(5) |
Oct
(4) |
Nov
|
Dec
(9) |
2025 |
Jan
(29) |
Feb
(4) |
Mar
(1) |
Apr
|
May
(10) |
Jun
(10) |
Jul
(15) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: John C. <yot...@gm...> - 2025-07-25 05:08:07
|
My examples work okay for the most part, understanding that I added an extra point to the spine. I tested the jsdelivr and x3dom.org “production” versions. I also only tested on my phone so far. Thanks for your work on this area, Andreas, maybe eventually I’ll have a pp3.x3d and pp3.json eventually where scripting is working in both X_ITE and X3DOM. On Thu, Jul 24, 2025 at 10:07 PM John Carlson <yot...@gm...> wrote: > I’ll probably test extrusions sometime tonight, the examples I have are > qq3 and pp3 (pp3 is more comprehensive, at this site: Be sure to select > X3DOM version for comparison. > > https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html > > I plan to work on a phone version, there are caching issues and some > models cause a refresh, unfortunately, on iPhone. I believe the Mac > version can work appropriately. > > John > > On Thu, Jul 24, 2025 at 9:58 PM Andreas Plesch <and...@gm...> > wrote: > >> A new x3dom-dev version was released with Extrusion fixes, available at >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom-full.js >> <https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js> et al. >> >> jsdelivr also supports versioned links, by commit SHA hash. >> https://github.com/x3dom/x3dom-dev/commits/main/ lists all commits to >> the repository along with their SHA. For example, this latest version is >> also available at this fixed URL: >> >> >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev@19a788e003f12f66d5ba2b16fab8614762ed6f42/dist/x3dom-full.js >> >> Have fun with x3dom ! >> >> -Andreas >> >> On Thu, Jul 10, 2025 at 1:14 AM Andreas Plesch <and...@gm...> >> wrote: >> >>> Please note that the download link for the dev version of x3dom has >>> migrated from x3dom.org/download/dev (not updated) to >>> >>> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >>> or >>> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >>> >>> which is >>> automatically updated at >>> https://github.com/x3dom/x3dom-dev >>> for every merged PR at >>> https://github.com/x3dom/x3dom >>> >>> Have fun with x3dom ! >>> >>> Andreas >>> >> >> >> -- >> Andreas Plesch >> Waltham, MA 02453 >> _______________________________________________ >> X3dom-users mailing list >> X3d...@li... >> https://lists.sourceforge.net/lists/listinfo/x3dom-users >> > |
From: John C. <yot...@gm...> - 2025-07-25 03:07:55
|
I’ll probably test extrusions sometime tonight, the examples I have are qq3 and pp3 (pp3 is more comprehensive, at this site: Be sure to select X3DOM version for comparison. https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html I plan to work on a phone version, there are caching issues and some models cause a refresh, unfortunately, on iPhone. John On Thu, Jul 24, 2025 at 9:58 PM Andreas Plesch <and...@gm...> wrote: > A new x3dom-dev version was released with Extrusion fixes, available at > https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom-full.js > <https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js> et al. > > jsdelivr also supports versioned links, by commit SHA hash. > https://github.com/x3dom/x3dom-dev/commits/main/ lists all commits to the > repository along with their SHA. For example, this latest version is also > available at this fixed URL: > > > https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev@19a788e003f12f66d5ba2b16fab8614762ed6f42/dist/x3dom-full.js > > Have fun with x3dom ! > > -Andreas > > On Thu, Jul 10, 2025 at 1:14 AM Andreas Plesch <and...@gm...> > wrote: > >> Please note that the download link for the dev version of x3dom has >> migrated from x3dom.org/download/dev (not updated) to >> >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >> or >> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >> >> which is >> automatically updated at >> https://github.com/x3dom/x3dom-dev >> for every merged PR at >> https://github.com/x3dom/x3dom >> >> Have fun with x3dom ! >> >> Andreas >> > > > -- > Andreas Plesch > Waltham, MA 02453 > _______________________________________________ > X3dom-users mailing list > X3d...@li... > https://lists.sourceforge.net/lists/listinfo/x3dom-users > |
From: Andreas P. <and...@gm...> - 2025-07-25 02:57:43
|
A new x3dom-dev version was released with Extrusion fixes, available at https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom-full.js <https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js> et al. jsdelivr also supports versioned links, by commit SHA hash. https://github.com/x3dom/x3dom-dev/commits/main/ lists all commits to the repository along with their SHA. For example, this latest version is also available at this fixed URL: https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev@19a788e003f12f66d5ba2b16fab8614762ed6f42/dist/x3dom-full.js Have fun with x3dom ! -Andreas On Thu, Jul 10, 2025 at 1:14 AM Andreas Plesch <and...@gm...> wrote: > Please note that the download link for the dev version of x3dom has > migrated from x3dom.org/download/dev (not updated) to > > https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) > or > https://x3dom.github.io/x3dom-dev/dist/x3dom.js > > which is > automatically updated at > https://github.com/x3dom/x3dom-dev > for every merged PR at > https://github.com/x3dom/x3dom > > Have fun with x3dom ! > > Andreas > -- Andreas Plesch Waltham, MA 02453 |
From: John C. <yot...@gm...> - 2025-07-17 23:11:30
|
If someone wants to upgrade to X3DOM, great! https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/data/x3dconnectorProto.x3d |
From: John C. <yot...@gm...> - 2025-07-15 14:02:09
|
What are various X3DOM production links? I've got a pulldown to change X3DOM versions on my main_viewer.html. Currently, everything is development. Might as well provide all of them! Thanks, John On Sun, Jul 13, 2025 at 1:22 PM Don Brutzman via x3d-public < x3d...@we...> wrote: > Andreas writes on 10 JUL 2025: > >> I have deployed a new dev version. >> Please note that the download link for the dev version of x3dom has >> migrated from x3dom.org/download/dev (not updated) to >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >> or >> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >> which is >> automatically updated through >> https://github.com/x3dom/x3dom-dev >> for every merged PR at >> https://github.com/x3dom/x3dom >> The netlify link is obsolete. > > >> Andreas > > > Thanks for the alert. I am hoping to get the address and invocation > correct in our X3D Example Archives scenes by updating the conversion > stylesheet. > > - X3D Example Archives > - https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples > - > https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt > > The X3dToX3domX_ITE.xslt stylesheet produces the following header in these > examples: > > - X3D Example Archives: X3D4WA, X3D for Web Authors, Chapter 01 > Technical Overview, Hello World > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldIndex.html > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldX3dom.xhtml > > <!DOCTYPE html> > > <!-- =================================================================== > --> > > <!-- embedded X3D scene appears after html/head/script and style entries > --> > > <!-- =================================================================== > --> > > <html xmlns="http://www.w3.org/1999/xhtml"> > > <head> > > <title>Hello World!, HelloWorld.x3d (X3DOM)</title> > > <meta http-equiv="X-UA-Compatible" content="chrome=1,IE=edge"/> > > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > > <meta name="generator" > > content="https://www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt"/> > > <script type="text/javascript" src=" > https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"> > </script> > > <!-- Numbered X3DOM release versions: https://www.x3dom.org/download --> > > <!-- Developer X3DOM release version: https://www.x3dom.org/download/dev > --> > > <link rel="stylesheet" > > type="text/css" > > href="https://x3dom.org/download/dev/x3dom.css"/> > > <script type="text/javascript" > > src="https://x3dom.org/download/dev/x3dom-full.js"/> > > > Questions please, before I start a major rebuild: > > 1. *x3dom.js or x3dom-full.js ? (both look to be available)* > 2. *Same treatment for x3dom.css or is it no longer used?* > 3. *What is up-to-date guidance whenText node is included?* I have > > > - "X3DOM Text Example > The following scenes demonstrate the use of the text and fontsyle > nodes. You can also use web fonts, however on windows there is a glitch. > You have to use and display the font in your document before you can use > them in X3DOM." > - https://x3dom.org/x3dom/example/x3dom_text.html > > <meta name="warning" > > content="Webfonts must be loaded prior to using Text node in X3D scene... > see https://x3dom.org/x3dom/example/x3dom_text.html"/> > > <!-- X3DOM needs Web Fonts when an X3D Text node is included --> > > <!-- adapted from https://x3dom.org/x3dom/example/x3dom_text.html and > https://web.mit.edu/jmorzins/www/fonts.html --> > > <style type="text/css"> > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SERIF'; /* default original */ > > font-style: normal; > > font-weight: 700; > > src: local('Roman'), url('Roman.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SERIF'; /* default alternate */ > > font-style: normal; > > font-weight: 700; > > src: local('Times New Roman'), local('TimesNewRoman'), url('Times New > Roman.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SANS'; /* default original */ > > font-style: normal; > > font-weight: 400; > > src: local('Arial'), url('Arial.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SANS'; /* default alternate */ > > font-style: normal; > > font-weight: 400; > > src: local('Helvetica'), url('Helvetica.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'TYPEWRITER'; /* default original */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier'), url('Courier.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'TYPEWRITER'; /* default alternate */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier New'), url('Courier New.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > </style> > > <style type="text/css" media="screen, print"> > > .webfont { font-size:200%; font-family:'TYPEWRITER'; color:green;} /* > Conversion TODO font families: SANS SERIF TYPEWRITER */ > > </style> > > and > > *4. Is the following still the best up-to-date list of supported nodes?* > > https://andreasplesch.github.io/x3dom/dist/doc/author/nodes.html > > P.S. node wish list: IndexedTriangleFanSet, Script > > Thanks in advance for all improvements to these invocations, and thanks as > ever for ongoing progress with X3DOM! > > all the best, Don > _______________________________________________ > x3d-public mailing list > x3d...@we... > http://web3d.org/mailman/listinfo/x3d-public_web3d.org > |
From: Andreas P. <and...@gm...> - 2025-07-14 03:45:39
|
Answers below. On Sun, Jul 13, 2025 at 2:21 PM Don Brutzman <don...@gm...> wrote: > Andreas writes on 10 JUL 2025: > >> I have deployed a new dev version. >> Please note that the download link for the dev version of x3dom has >> migrated from x3dom.org/download/dev (not updated) to >> https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) >> or >> https://x3dom.github.io/x3dom-dev/dist/x3dom.js >> which is >> automatically updated through >> https://github.com/x3dom/x3dom-dev >> for every merged PR at >> https://github.com/x3dom/x3dom >> The netlify link is obsolete. > > >> Andreas > > > Thanks for the alert. I am hoping to get the address and invocation > correct in our X3D Example Archives scenes by updating the conversion > stylesheet. > > - X3D Example Archives > - https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples > - > https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt > > The X3dToX3domX_ITE.xslt stylesheet produces the following header in these > examples: > > - X3D Example Archives: X3D4WA, X3D for Web Authors, Chapter 01 > Technical Overview, Hello World > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldIndex.html > - > https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter01TechnicalOverview/HelloWorldX3dom.xhtml > > <!DOCTYPE html> > > <!-- =================================================================== > --> > > <!-- embedded X3D scene appears after html/head/script and style entries > --> > > <!-- =================================================================== > --> > > <html xmlns="http://www.w3.org/1999/xhtml"> > > <head> > > <title>Hello World!, HelloWorld.x3d (X3DOM)</title> > > <meta http-equiv="X-UA-Compatible" content="chrome=1,IE=edge"/> > > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > > <meta name="generator" > > content="https://www.web3d.org/x3d/stylesheets/X3dToX3domX_ITE.xslt"/> > > <script type="text/javascript" src=" > https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"> > </script> > > <!-- Numbered X3DOM release versions: https://www.x3dom.org/download --> > > <!-- Developer X3DOM release version: https://www.x3dom.org/download/dev > --> > > <link rel="stylesheet" > > type="text/css" > > href="https://x3dom.org/download/dev/x3dom.css"/> > > <script type="text/javascript" > > src="https://x3dom.org/download/dev/x3dom-full.js"/> > > > Questions please, before I start a major rebuild: > > 1. *x3dom.js or x3dom-full.js ? (both look to be available)* > > x3dom-full.js > > 1. *Same treatment for x3dom.css or is it no longer used?* > > Yes, same treatment. It is still used. > > 1. *What is up-to-date guidance whenText node is included?* I have > > > - "X3DOM Text Example > The following scenes demonstrate the use of the text and fontsyle > nodes. You can also use web fonts, however on windows there is a glitch. > You have to use and display the font in your document before you can use > them in X3DOM." > - https://x3dom.org/x3dom/example/x3dom_text.html > > <meta name="warning" > > content="Webfonts must be loaded prior to using Text node in X3D scene... > see https://x3dom.org/x3dom/example/x3dom_text.html"/> > > <!-- X3DOM needs Web Fonts when an X3D Text node is included --> > > <!-- adapted from https://x3dom.org/x3dom/example/x3dom_text.html and > https://web.mit.edu/jmorzins/www/fonts.html --> > > <style type="text/css"> > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SERIF'; /* default original */ > > font-style: normal; > > font-weight: 700; > > src: local('Roman'), url('Roman.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SERIF'; /* default alternate */ > > font-style: normal; > > font-weight: 700; > > src: local('Times New Roman'), local('TimesNewRoman'), url('Times New > Roman.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'SANS'; /* default original */ > > font-style: normal; > > font-weight: 400; > > src: local('Arial'), url('Arial.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'SANS'; /* default alternate */ > > font-style: normal; > > font-weight: 400; > > src: local('Helvetica'), url('Helvetica.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > @font-face { > > font-family: 'TYPEWRITER'; /* default original */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier'), url('Courier.ttf') format('truetype'); > > } > > @font-face { > > font-family: 'TYPEWRITER'; /* default alternate */ > > font-style: normal; > > font-weight: 900; > > src: local('Courier New'), url('Courier New.ttf') format('truetype'); > > } > > /* > ============================================================================= > */ > > </style> > > <style type="text/css" media="screen, print"> > > .webfont { font-size:200%; font-family:'TYPEWRITER'; color:green;} /* > Conversion TODO font families: SANS SERIF TYPEWRITER */ > > </style> > > I think this guidance still applies for custom font families if a FontLibrary node is not used. FontLibrary font loading does not require this css. Also, all basic X3D font families do not require css. https://github.com/x3dom/x3dom/blob/master/test/functional/fonts.html has examples. > and > > *4. Is the following still the best up-to-date list of supported nodes?* > > https://andreasplesch.github.io/x3dom/dist/doc/author/nodes.html > > P.S. node wish list: IndexedTriangleFanSet, Script > > https://x3dom.github.io/x3dom-dev/dist/doc would be the best source for up to date documentation on supported nodes with dev releases as it is built and deployed along with the library. Thanks in advance for all improvements to these invocations, and thanks as > ever for ongoing progress with X3DOM! > > all the best, Don > All the best, Andreas -- Andreas Plesch Waltham, MA 02453 |
From: Andreas P. <and...@gm...> - 2025-07-10 05:15:01
|
Please note that the download link for the dev version of x3dom has migrated from x3dom.org/download/dev (not updated) to https://cdn.jsdelivr.net/gh/x3dom/x3dom-dev/dist/x3dom.js (preferred) or https://x3dom.github.io/x3dom-dev/dist/x3dom.js which is automatically updated at https://github.com/x3dom/x3dom-dev for every merged PR at https://github.com/x3dom/x3dom Have fun with x3dom ! Andreas |
From: John C. <yot...@gm...> - 2025-07-06 22:58:46
|
Apologies, the link behind the text was wrong. I confirmed that Y-axis extrusions works. Here’s the full file: https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/data/pp3.json I will make changes, and hopefully I won’t run into trouble. I realize this example has Scripts, AFAIK, and won’t interact properly in X3DOM. That wasn’t why I created another example so the issue could be focused on. There’s no need to work on this version, please apply any work to x3dom. (Full text) { "X3D": { "encoding":"UTF-8", "@profile":"Immersive", "@version":"4.0", "@xsd:noNamespaceSchemaLocation":" https://www.web3d.org/specifications/x3d-4.0.xsd", "JSON schema":" https://www.web3d.org/specifications/x3d-4.0-JSONSchema.autogenerated.json", "head": { "meta": [ { "@name":"title", "@content":"pp3.x3d" }, { "@name":"creator", "@content":"John Carlson" }, { "@name":"translator", "@content":"John Carlson" }, { "@name":"created", "@content":"5 May 2015" }, { "@name":"modified", "@content":"23 Dec 2022" }, { "@name":"description", "@content":"A process pipeline between three spheres (try typing on spheres and blue" }, { "@name":"identifier", "@content":"https://coderextreme.net/x3d/pp3.x3d" }, { "@name":"generator", "@content":"manual" }, { "@name":"translated", "@content":"26 June 2025" }, { "@name":"generator", "@content":"X3dToJson.xslt, https://www.web3d.org/x3d/stylesheets/X3dToJson.html" }, { "@name":"reference", "@content":"X3D JSON encoding: https://www.web3d.org/wiki/index.php/X3D_JSON_Encoding" } ] }, "Scene": { "-children":[ { "ProtoDeclare": { "@name":"Process", "ProtoBody": { "-children":[ { "Group": { "-children":[ { "#comment":"left" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0.7,1,0], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[-2.5,0,0,-1.5,0,0] } } } }, { "#comment":"<Transform translation=\"-2.5 0 0\"> <Shape> <Text DEF=\"LeftString\" string='\"l\"'/> </Shape> </Transform> <StringSensor DEF=\"LeftSensor\" enabled=\"false\"/> <TouchSensor DEF=\"LeftTouch\" enabled=\"true\"/>" } ] } }, { "#comment":"right" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0,0.7,1], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[1.5,0,0,2.5,0,0] } } } }, { "Transform": { "@translation":[2,0,0], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@DEF":"MaterialLightBlue", "@diffuseColor":[1,1,1] } } } }, "-geometry": { "Text": { "@DEF":"RightString", "@string":["r"] } } } } ] } }, { "StringSensor": { "@DEF":"RightSensor", "@enabled":false } }, { "TouchSensor": { "@description":"touch to activate", "@DEF":"RightTouch" } } ] } }, { "#comment":"up" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0,0.7,1], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[0,1.5,0,0,2.5,0] } } } }, { "Transform": { "@translation":[-0.5,2,0], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@USE":"MaterialLightBlue" } } } }, "-geometry": { "Text": { "@DEF":"UpString", "@string":["u"] } } } } ] } }, { "StringSensor": { "@DEF":"UpSensor", "@enabled":false } }, { "TouchSensor": { "@description":"touch to activate", "@DEF":"UpTouch" } } ] } }, { "#comment":"down" }, { "Transform": { "@scale":[0.5,0.5,0.5], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[0.7,1,0], "@transparency":0.5 } } } }, "-geometry": { "Extrusion": { "@creaseAngle":0.785, "@crossSection":[1,0,0.92,-0.38,0.71,-0.71,0.38,-0.92,0,-1,-0.38,-0.92,-0.71,-0.71,-0.92,-0.38,-1,0,-0.92,0.38,-0.71,0.71,-0.38,0.92,0,1,0.38,0.92,0.71,0.71,0.92,0.38,1,0], "@spine":[0,-2.5,0,0,-1.5,0] } } } }, { "#comment":"<Transform translation=\"-0.5 -2.5 0\"> <Shape> <Text DEF=\"DownString\" string='\"d\"'/> </Shape> </Transform> <StringSensor DEF=\"DownSensor\" enabled=\"false\"/> <TouchSensor description='touch to activate' DEF=\"DownTouch\" enabled=\"true\"/>" } ] } }, { "#comment":"center" }, { "Transform": { "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@diffuseColor":[1,0,0.7] } } } }, "-geometry": { "Sphere": { } } } }, { "Transform": { "@scale":[0.5,0.5,0.5], "@translation":[-0.5,0,1], "-children":[ { "Shape": { "-appearance": { "Appearance": { "-material": { "Material": { "@USE":"MaterialLightBlue" } } } }, "-geometry": { "Text": { "@DEF":"CenterString" } } } } ] } }, { "StringSensor": { "@DEF":"CenterSensor", "@enabled":false } }, { "TouchSensor": { "@description":"touch to activate", "@DEF":"CenterTouch" } } ] } } ] } }, { "Script": { "@DEF":"RightSingleToMultiString", "field": [ { "@name":"set_rightstring", "@accessType":"inputOnly", "@type":"SFString" }, { "@name":"rightlines", "@accessType":"outputOnly", "@type":"MFString" } ], "#sourceCode":[ "", "ecmascript:", "", "function initialize() {", "\trightlines = new MFString(\"\");", "}", "", "function set_rightstring(rightstr) {", "\trightlines = new MFString(rightstr);", "}", "" ] } }, { "Script": { "@DEF":"UpSingleToMultiString", "field": [ { "@name":"set_upstring", "@accessType":"inputOnly", "@type":"SFString" }, { "@name":"uplines", "@accessType":"outputOnly", "@type":"MFString" } ], "#sourceCode":[ "", "ecmascript:", "", "function initialize() {", "\tuplines = new MFString(\"\");", "}", "", "function set_upstring(upstr) {", "\tuplines = new MFString(upstr);", "}", "" ] } }, { "Script": { "@DEF":"CenterSingleToMultiString", "field": [ { "@name":"set_centerstring", "@accessType":"inputOnly", "@type":"SFString" }, { "@name":"centerlines", "@accessType":"outputOnly", "@type":"MFString" } ], "#sourceCode":[ "", "ecmascript:", "", "function initialize() {", "\tcenterlines = new MFString(\"\");", "}", "", "function set_centerstring(centerstr) {", "\tcenterlines = new MFString(centerstr);", "}", "" ] } }, { "ROUTE": { "@fromField":"enteredText", "@fromNode":"CenterSensor", "@toField":"set_centerstring", "@toNode":"CenterSingleToMultiString" } }, { "ROUTE": { "@fromField":"centerlines", "@fromNode":"CenterSingleToMultiString", "@toField":"set_string", "@toNode":"CenterString" } }, { "ROUTE": { "@fromField":"isOver", "@fromNode":"CenterTouch", "@toField":"set_enabled", "@toNode":"CenterSensor" } }, { "ROUTE": { "@fromField":"enteredText", "@fromNode":"RightSensor", "@toField":"set_rightstring", "@toNode":"RightSingleToMultiString" } }, { "ROUTE": { "@fromField":"rightlines", "@fromNode":"RightSingleToMultiString", "@toField":"set_string", "@toNode":"RightString" } }, { "ROUTE": { "@fromField":"isOver", "@fromNode":"RightTouch", "@toField":"set_enabled", "@toNode":"RightSensor" } }, { "ROUTE": { "@fromField":"enteredText", "@fromNode":"UpSensor", "@toField":"set_upstring", "@toNode":"UpSingleToMultiString" } }, { "ROUTE": { "@fromField":"uplines", "@fromNode":"UpSingleToMultiString", "@toField":"set_string", "@toNode":"UpString" } }, { "ROUTE": { "@fromField":"isOver", "@fromNode":"UpTouch", "@toField":"set_enabled", "@toNode":"UpSensor" } } ] } } }, { "NavigationInfo": { } }, { "Viewpoint": { "@description":"Process pipes", "@orientation":[1,0,0,-0.4], "@position":[0,5,12] } }, { "Transform": { "@translation":[0,-2.5,0], "-children":[ { "ProtoInstance": { "@name":"Process" } } ] } }, { "Transform": { "-children":[ { "ProtoInstance": { "@name":"Process" } } ] } }, { "Transform": { "@translation":[0,2.5,0], "-children":[ { "ProtoInstance": { "@name":"Process" } } ] } } ] } } } |
From: John C. <yot...@gm...> - 2025-07-06 04:51:29
|
It seems like X3DOM doesn’t do extrusion properly, at least according to successful renderings in other browsers. This is a long term issue, mentioned several times. This is one reason I don’t use X3DOM on a more regular basis. So I tried converting my extrusion to PLY, and things are even worse. I need: 1) a way to render extrusions properly in X3DOM. 2) a way to tessellate X3D XML/JSON Extrusions to PLY. I will put this on a feature request. John |
From: John C. <yot...@gm...> - 2025-07-03 07:18:16
|
I am adding tessellattion to my project, particularly converting X3D JSON to PLY. Here's a picture of a sphere in X3DOM (rubk.json or rubik.x3d converted to PLY, then back to XML or JSON for viewing in X3DOM): [image: image.png] So this might be the source of the split in my flowers code? which takes a Sphere, and manipulates the surface by offsetting the points of the surface with a shader. Here's my current Gemini Pro 2.5 tessellation code (perhaps derived from Three.js or X3DOM? I haven't looked): function tessellateSphere(node, options) { /* ... (Unchanged) ... */ const r = node['@radius'] ? parseFloat(node['@radius']) : 1; const sub = options.subdivisions || 24; const verts=[], faces=[]; for (let j=0;j<=sub;j++){let aj=j*Math.PI/sub,sj=Math.sin(aj),cj=Math.cos(aj); for(let i=0;i<=sub;i++){let ai=i*2*Math.PI/sub,si=Math.sin(ai),ci=Math.cos(ai); verts.push([r*si*sj,r*cj,r*ci*sj]);}} for(let j=0;j<sub;j++){for(let i=0;i<sub;i++){let p1=j*(sub+1)+i,p2=p1+1,p3=(j+1)*(sub+1)+i,p4=p3+1; faces.push([p1,p2,p4]); faces.push([p1,p4,p3]);}} return { vertices: verts, faces: faces }; } Any better tessellation welcome! I'm going to ask Claude for better code. John |
From: John C. <yot...@gm...> - 2025-07-02 22:33:35
|
I did some searching in Vince’s index.html, and found: https://x3dom.org/release/x3dom-full.js I hope this resolves Andreas and my queries. Now the question is, should I put this production release in my app, and include all versions of X3DOM? Whereas, previously, I only included versions from my app. Thinking, John On Tue, Jul 1, 2025 at 1:09 PM John Carlson <yot...@gm...> wrote: > Vince, would it be possible to include your x3dom in the X3DJSONLD main > viewer? > > https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html > > See X3DOM versions. > > If agreeable, please provide a web-link to raw JavaScript code (something > like …/x3dom-full.debug.js). > > > On Tue, Jul 1, 2025 at 12:22 PM vmarchetti--- via x3d-public < > x3d...@we...> wrote: > >> Sorry, I should have replied earlier — >> The x3dom based IIIF manifest viewer code is at >> https://github.com/vincentmarchetti/iiif-x3dom-demo ; the version of the >> page visible from “Manifestival” is in the >> Manifest-by-url branch at >> https://github.com/vincentmarchetti/iiif-x3dom-demo/tree/manifest-by-url >> >> So the manifestival page doesn’t perform any conversion itself, it just >> sends the manifest data (in json form) to each of the four viewers >> presented.. Each viewer was independently developed to render the manifest, >> in a similar way that our x3d viewers are independently developed in their >> own environments to read and render x3d encodings. >> >> >> >> Vince Marchetti >> >> >> On Jul 1, 2025, at 11:46 AM, Andreas Plesch via x3d-public < >> x3d...@we...> wrote: >> >> It turns out that Morphosource repos do not include the viewers. I >> could not find the source repo for the x3d converter and x3dom viewer >> they are using. >> >> -Andreas >> >> On Mon, Jun 30, 2025 at 5:11 PM Andreas Plesch <and...@gm...> >> wrote: >> >> >> Very cool. Morphosource translates the model manifests with metadata >> into x3dom, and other formats: >> >> https://morphosource.github.io/manifestival/ >> >> Perhaps they accept pull requests. >> >> Cheers, -Andreas >> >> On Mon, Jun 30, 2025 at 3:00 PM <x3d...@we...> wrote: >> >> >> Send x3d-public mailing list submissions to >> x3d...@we... >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org >> or, via email, send a message with subject or body 'help' to >> x3d...@we... >> >> You can reach the person managing the list at >> x3d...@we... >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of x3d-public digest..." >> >> >> Today's Topics: >> >> 1. Review of IIIF efforts in 3D interoperability (Vincent Marchetti) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 30 Jun 2025 10:03:54 -0400 >> From: Vincent Marchetti <vma...@ks...> >> To: X3D-Public <x3d...@we...> >> Subject: [x3d-public] Review of IIIF efforts in 3D interoperability >> Message-ID: <B52...@ks...> >> Content-Type: text/plain; charset=us-ascii >> >> Tom Flynn has prepared a summary of the IIIF 3D groups progress in >> developing version 4 of their API for presenting 3D models in the cultural >> heritage world. >> >> This post presents progress presented at the recent (June 2025) IIIF >> meeting in Leeds, UK >> >> read all about at >> https://nebulousflynn.substack.com/p/interoperable-accesible-portable ; >> it includes demonstration links including to an X3D/X3DOM implementation >> of the draft standard manifest viewer >> >> Vince Marchetti >> >> >> >> >> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> x3d-public mailing list >> x3d...@we... >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org >> >> >> ------------------------------ >> >> End of x3d-public Digest, Vol 195, Issue 31 >> ******************************************* >> >> >> >> >> -- >> Andreas Plesch >> Waltham, MA 02453 >> >> >> >> >> -- >> Andreas Plesch >> Waltham, MA 02453 >> >> _______________________________________________ >> x3d-public mailing list >> x3d...@we... >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org >> >> >> _______________________________________________ >> x3d-public mailing list >> x3d...@we... >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org >> > |
From: John C. <yot...@gm...> - 2025-06-29 12:59:42
|
But landscape mode on iPhone is workable once you know the layout. On Sat, Jun 28, 2025 at 4:26 PM John Carlson <yot...@gm...> wrote: > Sorry folks, looks awful on phone, I can do better. Try chrome or edge > but not on iPhone. > > Joh > > On Sat, Jun 28, 2025 at 3:37 PM John Carlson <yot...@gm...> wrote: > >> https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html >> >> With some features like better file selection, file filtering >> (client-side here, serverside planned), file hierarchy, >> >> I wanted my "friend" to analyze all the X3DOM instances out there for >> prototype processors, but instead, my "friend" suggested having a pulldown >> for all the X3DOM versions (well, the modern ones), so with my "friend's" >> help, that got easily implemented, it just required me to remind my >> "friend" to do a reload when the version changes. Does it really do >> anything? Maybe someone who knows could try it out? Andreas? I'm not >> aware of any differences. >> >> PLY is still the poorman out with no conversion from JSON, and I still >> don't tessellate when converting to STL. >> >> All the plumbing is basically the same as the recent push. >> >> So with my friend or foible, I'll try to get some features in, like >> better support for PLY and STL. There's a PLY file that won't convert, for >> example. Plus, My qq3.x3d extrusions still don't work well in any version >> of X3DOM (see X_ITE) >> >> Looking forward to getting Castle-Model-Mobile-Viewer involved, I have a >> place for it! Maybe in beta or final release? >> >> Maybe eventually, I'll build a launcher for JSONverse communities. >> >> If anyone wants to offer tabs for different bindings and encodings, I'm >> game. The infrastructure is nearly there. >> >> >> John >> > |
From: John C. <yot...@gm...> - 2025-06-29 12:33:10
|
I think this got figured out by reloading after switching the version of X3DOM (interactively, not in the editor). Probably an unusual case! John On Sat, Jun 28, 2025 at 8:56 AM John Carlson <yot...@gm...> wrote: > [image: image.png] > |
From: John C. <yot...@gm...> - 2025-06-29 12:16:25
|
What I’d like to do is JSON -> DOM -> Proto processor-> JSON -> STL, but there’s a possible infinite loop in that I haven’t figured out yet. Plus I need to enable STL -> JSON processing when not loading a file. A lot of work to do. John On Fri, Jun 27, 2025 at 1:42 PM John Carlson <yot...@gm...> wrote: > The issue is, if I convert an X3D Rubik’s cube of protos, I only get one > cube in STL. > > I will see what I can do by converting DOM, but perhaps the problem is > that I’m converting original JSON without my proto expander. Oops, I > deleted it! > > John > > On Fri, Jun 27, 2025 at 9:06 AM Andreas Plesch <and...@gm...> > wrote: > >> Hi John, >> >> I believe there is a way in x3dom to access the populated protobody of a >> protoinstance if that is what you trying to extract. It is a property of >> the protoinstance dom node which you may be able to find. I do not recall >> the details but the browser devtools would help in exploring the full dom >> object. >> >> Hope this helps, >> >> Andreas >> >> On Thu, Jun 26, 2025, 5:33 PM John Carlson <yot...@gm...> wrote: >> >>> In X3DOM or X_ITE, is the post Proto processor XML or DOM available? >>> Such that I can convert to STL, which doesn’t have protos? >>> >>> Thanks! >>> >>> John >>> >> |
From: John C. <yot...@gm...> - 2025-06-28 21:26:32
|
Sorry folks, looks awful on phone, I can do better. Try chrome or edge but not on iPhone. Joh On Sat, Jun 28, 2025 at 3:37 PM John Carlson <yot...@gm...> wrote: > https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html > > With some features like better file selection, file filtering (client-side > here, serverside planned), file hierarchy, > > I wanted my "friend" to analyze all the X3DOM instances out there for > prototype processors, but instead, my "friend" suggested having a pulldown > for all the X3DOM versions (well, the modern ones), so with my "friend's" > help, that got easily implemented, it just required me to remind my > "friend" to do a reload when the version changes. Does it really do > anything? Maybe someone who knows could try it out? Andreas? I'm not > aware of any differences. > > PLY is still the poorman out with no conversion from JSON, and I still > don't tessellate when converting to STL. > > All the plumbing is basically the same as the recent push. > > So with my friend or foible, I'll try to get some features in, like better > support for PLY and STL. There's a PLY file that won't convert, for > example. Plus, My qq3.x3d extrusions still don't work well in any version > of X3DOM (see X_ITE) > > Looking forward to getting Castle-Model-Mobile-Viewer involved, I have a > place for it! Maybe in beta or final release? > > Maybe eventually, I'll build a launcher for JSONverse communities. > > If anyone wants to offer tabs for different bindings and encodings, I'm > game. The infrastructure is nearly there. > > > John > |
From: John C. <yot...@gm...> - 2025-06-28 20:38:19
|
https://coderextreme.net/X3DJSONLD/src/main/html/main_viewer.html With some features like better file selection, file filtering (client-side here, serverside planned), file hierarchy, I wanted my "friend" to analyze all the X3DOM instances out there for prototype processors, but instead, my "friend" suggested having a pulldown for all the X3DOM versions (well, the modern ones), so with my "friend's" help, that got easily implemented, it just required me to remind my "friend" to do a reload when the version changes. Does it really do anything? Maybe someone who knows could try it out? Andreas? I'm not aware of any differences. PLY is still the poorman out with no conversion from JSON, and I still don't tessellate when converting to STL. All the plumbing is basically the same as the recent push. So with my friend or foible, I'll try to get some features in, like better support for PLY and STL. There's a PLY file that won't convert, for example. Plus, My qq3.x3d extrusions still don't work well in any version of X3DOM (see X_ITE) Looking forward to getting Castle-Model-Mobile-Viewer involved, I have a place for it! Maybe in beta or final release? Maybe eventually, I'll build a launcher for JSONverse communities. If anyone wants to offer tabs for different bindings and encodings, I'm game. The infrastructure is nearly there. John |
From: John C. <yot...@gm...> - 2025-06-28 13:56:48
|
[image: image.png] |
From: John C. <yot...@gm...> - 2025-06-27 18:42:22
|
The issue is, if I convert an X3D Rubik’s cube of protos, I only get one cube in STL. I will see what I can do by converting DOM, but perhaps the problem is that I’m converting original JSON without my proto expander. Oops, I deleted it! John On Fri, Jun 27, 2025 at 9:06 AM Andreas Plesch <and...@gm...> wrote: > Hi John, > > I believe there is a way in x3dom to access the populated protobody of a > protoinstance if that is what you trying to extract. It is a property of > the protoinstance dom node which you may be able to find. I do not recall > the details but the browser devtools would help in exploring the full dom > object. > > Hope this helps, > > Andreas > > On Thu, Jun 26, 2025, 5:33 PM John Carlson <yot...@gm...> wrote: > >> In X3DOM or X_ITE, is the post Proto processor XML or DOM available? >> Such that I can convert to STL, which doesn’t have protos? >> >> Thanks! >> >> John >> > |
From: Andreas P. <and...@gm...> - 2025-06-27 14:06:58
|
Hi John, I believe there is a way in x3dom to access the populated protobody of a protoinstance if that is what you trying to extract. It is a property of the protoinstance dom node which you may be able to find. I do not recall the details but the browser devtools would help in exploring the full dom object. Hope this helps, Andreas On Thu, Jun 26, 2025, 5:33 PM John Carlson <yot...@gm...> wrote: > In X3DOM or X_ITE, is the post Proto processor XML or DOM available? Such > that I can convert to STL, which doesn’t have protos? > > Thanks! > > John > |
From: John C. <yot...@gm...> - 2025-06-27 00:33:19
|
In X3DOM or X_ITE, is the post Proto processor XML or DOM available? Such that I can convert to STL, which doesn’t have protos? Thanks! John |
From: John C. <yot...@gm...> - 2025-06-26 13:57:26
|
Bug in: https://andreasplesch.github.io/x3dom/dist/x3dom-full.debug.js domNode is null Reminder is to test X3DJSONLD with https://coderextreme.net/X3DJSONLD/src/main/stl/UavBeehive.stl Copy/paste stl into STL textarea. Test against: https://coderextreme.net/X3DJSONLD/src/main/html/index3doim.html if you load ./slt/cleat_clamp.stl in the upper left, you will see the issue in the console. When it comes online. Click around on the "here"s to generate cases. Stack trace: Uncaught TypeError: Cannot read properties of null (reading 'childNodes') at x3dom.X3DDocument.removeX3DOMBackendGraph (x3dom-full.debug.js:22426:28) at x3dom.X3DDocument.<anonymous> (x3dom-full.debug.js:22704:18) at Array.forEach (<anonymous>) at x3dom.X3DDocument.onX3DNodeRemoved ( x3dom-full.debug.js:22696:14) at x3dom.X3DDocument.onX3DMutation ( x3dom-full.debug.js:22843:26) |