You can subscribe to this list here.
2011 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2012 |
Jan
(3) |
Feb
(3) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(3) |
Jul
(7) |
Aug
(18) |
Sep
(7) |
Oct
(6) |
Nov
(19) |
Dec
(10) |
2013 |
Jan
(6) |
Feb
(30) |
Mar
(12) |
Apr
(26) |
May
(32) |
Jun
(29) |
Jul
(2) |
Aug
(11) |
Sep
(12) |
Oct
(30) |
Nov
(13) |
Dec
(31) |
2014 |
Jan
(28) |
Feb
(16) |
Mar
(24) |
Apr
(29) |
May
(25) |
Jun
(28) |
Jul
(52) |
Aug
(23) |
Sep
(8) |
Oct
(80) |
Nov
(26) |
Dec
(62) |
2015 |
Jan
(58) |
Feb
(127) |
Mar
(14) |
Apr
(10) |
May
(3) |
Jun
(6) |
Jul
(7) |
Aug
(29) |
Sep
(6) |
Oct
(9) |
Nov
(30) |
Dec
(17) |
2016 |
Jan
(41) |
Feb
(16) |
Mar
(19) |
Apr
(7) |
May
(7) |
Jun
(34) |
Jul
(19) |
Aug
(13) |
Sep
(8) |
Oct
(11) |
Nov
(1) |
Dec
(4) |
2017 |
Jan
(2) |
Feb
(8) |
Mar
(8) |
Apr
(4) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(20) |
Oct
(7) |
Nov
(5) |
Dec
(1) |
2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(16) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
|
May
(6) |
Jun
|
Jul
(9) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(17) |
Dec
(9) |
2021 |
Jan
(9) |
Feb
|
Mar
|
Apr
(3) |
May
(13) |
Jun
(13) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2023 |
Jan
(12) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(5) |
Jul
|
Aug
(6) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Brutzman, D. (D. (CIV) <bru...@np...> - 2024-03-05 21:18:42
|
Not finding LoadSensor in list of supported nodes. * https://doc.x3dom.org/author/nodes.html * X3D 4.0 Architecture, Networking component, 9.4.3LoadSensor * https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/compon ents/networking.html#LoadSensor Example scene for testing: * X3D Example Archives: Humanoid Animation, Winter And Spring, Main Stage * https://www.web3d.org/x3d/content/examples/HumanoidAnimation/WinterAndSpring /MainStageIndex.html * https://www.web3d.org/x3d/content/examples/HumanoidAnimation/WinterAndSpring /MainStage.x3d Thanks for all of the great efforts! all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br bru...@np... Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, navy robotics https://faculty.nps.edu/brutzman |
From: Web3D C. <ann...@we...> - 2023-10-03 00:32:48
|
Web3D 2023 on-line and in-person registration still open. Web3D 2023: Join us to advance the exciting world of 3D on the Web! Web3D 2023 Conference (https://web3d.siggraph.org/) , 9-11 October 2023, in beautiful San Sebastian, Spain. In-person and on-line registration still open! Register now (https://web3d.siggraph.org/2023-registration/) ! Join us to advance the exciting world of 3D on the Web! Learn from the best in the 3D industry. Generate new knowledge and unlock the value of 3D across several application domains. Program Highlights (https://web3d.siggraph.org/program/) and Keynote Speakers (https://web3d.siggraph.org/program/#keynote) Metaverse - Digital Twins - AR/VR Simulation - Scientific Visualization https://web3d.siggraph.org/program/ See you in San Sebastián! If you would like more information about the conference, please visit our website (https://web3d.siggraph.org/) . Learn More (https://web3d.siggraph.org/) ============================================================ ** Facebook (http://www.facebook.com) ** Twitter (https://twitter.com/Web3Dconsortium) ** YouTube (https://www.youtube.com/c/Web3DConsortium) ** Website (www.web3d.org) ** Email (mailto:we...@we...) Copyright © 2023 Web3D Consortium, All rights reserved. You are receiving this email because you opted in via our website. Our mailing address is: Web3D Consortium 133 Lorimer St Salinas, CA 93901-2021 USA Want to change how you receive these emails? You can ** update your preferences (https://web3d.us10.list-manage.com/profile?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=d11ff70006) or ** unsubscribe from this list (https://web3d.us10.list-manage.com/unsubscribe?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=d11ff70006) . Email Marketing Powered by Mailchimp http://www.mailchimp.com/email-referral/?utm_source=freemium_newsletter&utm_medium=email&utm_campaign=referral_marketing&aid=0051673b83909ae284624feb2&afl=1 |
From: Web3D C. <ann...@we...> - 2023-09-12 17:46:02
|
Announcing Keynote Speakers at the Web3D 2023 Conference, Mel Slater, Marius Preda and Francois Daoust Announcing Keynote Speakers at the Web3D 2023 Conference Introducing our Keynote Speakers (https://web3d.siggraph.org/program/#keynote) , Mel Slater, Marius Preda and Francois Daoust. Their contributions to the field of 3D Graphics have been transformative, and they continue to shape the future of this industry. They will provide new insights into the evolving world of 3D technologies and the metaverse. Early registration (https://web3d.siggraph.org/2023-registration/) is still open. We have an action packed Program (https://web3d.siggraph.org/program/) with research papers, workshops, tutorials, Industrial use cases and more. Enter our HAnim Music (https://web3d.siggraph.org/humanoid-animation-competition/) Animation competition (https://web3d.siggraph.org/humanoid-animation-competition/) (deadline Sept 22). Join us in-person in beautiful San Sebastian! or online. Mel Slater "Multi-person shared virtual environments, and implications for the metaverse" Mel Slater is a Distinguished Investigator at the University of Barcelona (https://web.ub.edu/web/ub/) in the Institute of Neurosciences (http://www.neurociencies.ub.edu/) , and co-Director of the Event Lab (https://www.event-lab.org/) (Experimental Virtual Environments for Neuroscience and Technology). He was previously Professor of Virtual Environments at University College London in the Department of Computer Science. He held a European Research Council Advanced Grant TRAVERSE 2009-2015 and has now a second Advanced Grant MoTIVE (https://www.motiverc.org/) 2018-2023. He is a Research Award Winner (https://en.wikipedia.org/wiki/Humboldt_Prize) (https://en.wikipedia.org/wiki/Humboldt_Prize) of the Alexander von Humboldt Foundation in 2021, and was elected to the IEEE VGTC Virtual Reality Academy (https://tc.computer.org/vgtc/awards/virtual-reality-academy/) in 2022. He is Field Editor of Frontiers in Virtual Reality (https://www.frontiersin.org/journals/virtual-reality) , and Chief Editor of the Human Behaviour in Virtual Reality (https://www.frontiersin.org/journals/virtual-reality/sections/virtual-reality-and-human-behaviour) section. His publications can be seen on publicationslist.org/melslater. He currently coordinates the European Metaverse Research Network (https://metaverse-research-network.info/) . Marius Preda "Compression factors for realistic 3D graphics" A distinguished Associate Professor with the Institut MINES-Télécom, Paris, Preda brings a rich academic background to the table. With degrees in engineering from the University POLITEHNICA of Bucharest and a Ph.D. in mathematics and computer science from University Paris V, Preda has been a formidable figure in the world of 3D Graphics. He is currently the Convenor of the MPEG 3D Graphics and Haptics Working Group of ISO and has contributed immensely to several international standards in fields of 3-D graphics coding, virtual worlds, and augmented reality. Francois Daoust "W3C and immersive 3D worlds in Web browsers – Evolutions of the Web platform" François Daoust is Media and Entertainment Champion at the World Wide Web Consortium (W3C), tracking and progressing activities of the W3C around the convergence between Web and media. This includes serving as W3C staff contact for the Media Working Group, Second Screen Working Group and GPU for the Web Working Group, exploring and organizing standardization workshops on topics of interest (Games on the Web, Professional media production), and liaising with other organizations on scenarios, needs, existing technical solutions, and identified gaps. Join us in-person or virtually! Take this opportunity to learn from the best in the industry and engage with a passionate community of like-minded enthusiasts. We thank our Platinum sponsor 3dMD (http://3dmd.com) and Gold Sponsors Khronos (http://khronos.org) . Let's come together to advance the exciting world of 3D on the Web! If you would like more information about the conference, please visit our website (https://web3d.siggraph.org/) . See you in San Sebastián! Learn More (https://www.web3d.siggraph.org) ============================================================ ** Facebook (http://www.facebook.com) ** Twitter (https://twitter.com/Web3Dconsortium) ** YouTube (https://www.youtube.com/c/Web3DConsortium) ** Website (www.web3d.org) ** Email (mailto:we...@we...) Copyright © 2023 Web3D Consortium, All rights reserved. You are receiving this email because you opted in via our website. Our mailing address is: Web3D Consortium 133 Lorimer St Salinas, CA 93901-2021 USA Want to change how you receive these emails? You can ** update your preferences (https://web3d.us10.list-manage.com/profile?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=a861ec6b32) or ** unsubscribe from this list (https://web3d.us10.list-manage.com/unsubscribe?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=a861ec6b32) . Email Marketing Powered by Mailchimp http://www.mailchimp.com/email-referral/?utm_source=freemium_newsletter&utm_medium=email&utm_campaign=referral_marketing&aid=0051673b83909ae284624feb2&afl=1 |
From: Web3D C. <ann...@we...> - 2023-08-31 21:16:54
|
Early registration ends 8th Sept 2023. Immersive 3D innovation at it's best! Web3D 2023: Collaborate, Network and Innovate. Join us in-person or on-line! Web3D 2023 Conference (https://web3d.siggraph.org/) , 9-11 October 2023, in San Sebastian, Spain. Sponsored by ACM SIGGRAPH (https://www.siggraph.org/) and hosted by Vicomtech (http://vicomtech.org) . Register (https://web3d.siggraph.org/2023-registration/) now and learn from the best in the 3D industry. Engage with a passionate community of like-minded enthusiasts. Join us to advance the exciting world of 3D on the Web! Program Details (https://web3d.siggraph.org/program/) Keynote Speakers (https://web3d.siggraph.org/#keynote) Papers: Presenting original work in 3D research and their applications. Posters: Interactive posters presenting results of ongoing or recently completed work in 3D web research and applications. Industrial Use Cases: Use cases aimed at demonstrating how 3D web technologies may be used in industrial applications. Tutorials: Courses presenting introductory and advanced applications of 3D Web technologies to students and to experienced practitioners. Workshops: Workshops providing a forum for researchers and practitioners from both the Web and 3D multimedia communities, to discuss and exchange positions on current and emergent 3D web topics. Competitions: An annual competition dedicated to showing how Humanoid Animation can be used for creating animated music videos. If you would like more information about the conference, please visit our website (https://web3d.siggraph.org/) . See you in San Sebastián! Learn More (https://web3d.siggraph.org/) ============================================================ ** Facebook (http://www.facebook.com) ** Twitter (https://twitter.com/Web3Dconsortium) ** YouTube (https://www.youtube.com/c/Web3DConsortium) ** Website (www.web3d.org) ** Email (mailto:we...@we...) Copyright © 2023 Web3D Consortium, All rights reserved. You are receiving this email because you opted in via our website. Our mailing address is: Web3D Consortium 133 Lorimer St Salinas, CA 93901-2021 USA Want to change how you receive these emails? You can ** update your preferences (https://web3d.us10.list-manage.com/profile?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=0ef0bf6503) or ** unsubscribe from this list (https://web3d.us10.list-manage.com/unsubscribe?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=0ef0bf6503) . Email Marketing Powered by Mailchimp http://www.mailchimp.com/email-referral/?utm_source=freemium_newsletter&utm_medium=email&utm_campaign=referral_marketing&aid=0051673b83909ae284624feb2&afl=1 |
From: Web3D C. <ann...@we...> - 2023-08-05 15:46:27
|
Learn how best to make the Metaverse fully interoperable with the WWW and the Standards ecosystem. Celebrate 50 Years of SIGGRAPH Conferences with Web3D Consortium Join the Web3D Consortium at SIGGRAPH 2023 (https://s2023.siggraph.org/) ( Aug 6-10, 2023 in Los Angeles) as we celebrate 28 years of breakthroughs in 3D Web technology along with 50 years of SIGGRAPH history. Attend Web3D (https://www.web3d.org/event/web3d-siggraph-2023) Birds of a Feather (BoF) (https://www.web3d.org/event/web3d-siggraph-2023) (https://www.web3d.org/event/web3d-siggraph-2023) discussions, bolstered by a community of innovators who have mapped the future of interactive, real-time 3D Graphics. Cartographic Visualization (Carto) BOF (https://s2023.siggraph.org/presentation/?id=villip_105&sess=sess339) - Highlighting the future of digital mapping to support our daily lives. Monday, August 7, Noon - 1:30 PM in the ACM SIGGRAPH Village Theater. X3D4 is Web3D Ready (https://s2023.siggraph.org/presentation/?id=bof_109&sess=sess192) - A major upgrade to the Extensible 3D (X3D) Graphics Monday, 7 August 2023 - 3:00 PM - 4:30 PM Pacific. Room 514. 3D Web Interoperability for the Metaverse (https://s2023.siggraph.org/presentation/?id=bof_108&sess=sess191) - How best to make the Metaverse fully interoperable with the WWW and the Standards ecosystem. Tuesday, 8 August 2023 - 1:00 PM - 3:00 PM Pacific. Room 514. Take this opportunity to learn from the best in the industry and engage with a passionate community of like-minded enthusiasts. Let's come together to advance the exciting world of 3D on the Web! If you would like more information about Web3D Standards and use cases please visit us at Web3D.org (https://web3d.org/) See you in Los Angeles! Learn More (https://www.web3d.org/event/web3d-siggraph-2023) ============================================================ ** Facebook (http://www.facebook.com) ** Twitter (https://twitter.com/Web3Dconsortium) ** YouTube (https://www.youtube.com/c/Web3DConsortium) ** Website (www.web3d.org) ** Email (mailto:we...@we...) Copyright © 2023 Web3D Consortium, All rights reserved. You are receiving this email because you opted in via our website. Our mailing address is: Web3D Consortium 133 Lorimer St Salinas, CA 93901-2021 USA Want to change how you receive these emails? You can ** update your preferences (https://web3d.us10.list-manage.com/profile?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=f63a8b2865) or ** unsubscribe from this list (https://web3d.us10.list-manage.com/unsubscribe?u=0051673b83909ae284624feb2&id=f1ef934431&e=43bd7983eb&c=f63a8b2865) . Email Marketing Powered by Mailchimp http://www.mailchimp.com/email-referral/?utm_source=freemium_newsletter&utm_medium=email&utm_campaign=referral_marketing&aid=0051673b83909ae284624feb2&afl=1 |
From: Nicholas P. <np...@vt...> - 2023-08-01 15:07:15
|
Congratulations!! This is very exciting news for the community. Thank you for all your efforts! We will be taking this good news and demos to SIGGRAPH next week!! :-) With best regards, n_polys On Tue, Aug 1, 2023, 8:18 AM Timo Sturm <tim...@th...> wrote: > We are happy to announce the release of X3DOM 1.8.3! This release contains > a handful of new features and improvements along with a number of bug fixes > since the last release. We would like to thank all users and, of course, > all the contributors, that make X3DOM such a great project. > > - New Features > - Add basic support for webXR > - Add support for PointProperties > - Add support for glTF draco extension > - Add support for EXPORT/IMPORT statements > - Add bboxDisplay field for X3DBoundedObject and x3dom custom > fields bboxMargin and bboxColor > - Fixes and Enhancements > - Automatic sortType based on auto texture channel count > - MovieTexture: autostart, ios and removal > - Support url field change for AudioClip > - Better indices for textured IFS with creases > - Ensure correct children order after ExternProto instancing > - Allow smooth creaseAngle during coord updates for IFS > - and more... > > For a detailed list of changes see the changelog on Github: > https://github.com/x3dom/x3dom/blob/stable/1.8.x/CHANGELOG.md > > Release download: > https://x3dom.org/download/1.8.3 > > -- > Timo > _______________________________________________ > X3dom-users mailing list > X3d...@li... > https://lists.sourceforge.net/lists/listinfo/x3dom-users > |
From: Timo S. <tim...@th...> - 2023-08-01 15:01:48
|
We are happy to announce the release of X3DOM 1.8.3! This release contains a handful of new features and improvements along with a number of bug fixes since the last release. We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project. * New Features * Add basic support for webXR * Add support for PointProperties * Add support for glTF draco extension * Add support for EXPORT/IMPORT statements * Add bboxDisplay field for X3DBoundedObject and x3dom custom fields bboxMargin and bboxColor * Fixes and Enhancements * Automatic sortType based on auto texture channel count * MovieTexture: autostart, ios and removal * Support url field change for AudioClip * Better indices for textured IFS with creases * Ensure correct children order after ExternProto instancing * Allow smooth creaseAngle during coord updates for IFS * and more... For a detailed list of changes see the changelog on Github: https://github.com/x3dom/x3dom/blob/stable/1.8.x/CHANGELOG.md Release download: https://x3dom.org/download/1.8.3 -- Timo |
From: Andreas P. <and...@gm...> - 2023-08-01 13:41:32
|
Thanks, Timo, for shepherding the release and making it happen ! Cheers, Andreas On Tue, Aug 1, 2023 at 8:18 AM Timo Sturm <tim...@th...> wrote: > > We are happy to announce the release of X3DOM 1.8.3! This release contains a handful of new features and improvements along with a number of bug fixes since the last release. We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project. > > New Features > > Add basic support for webXR > Add support for PointProperties > Add support for glTF draco extension > Add support for EXPORT/IMPORT statements > Add bboxDisplay field for X3DBoundedObject and x3dom custom fields bboxMargin and bboxColor > > Fixes and Enhancements > > Automatic sortType based on auto texture channel count > MovieTexture: autostart, ios and removal > Support url field change for AudioClip > Better indices for textured IFS with creases > Ensure correct children order after ExternProto instancing > Allow smooth creaseAngle during coord updates for IFS > and more... > > For a detailed list of changes see the changelog on Github: > https://github.com/x3dom/x3dom/blob/stable/1.8.x/CHANGELOG.md > > Release download: > https://x3dom.org/download/1.8.3 > > -- > Timo > _______________________________________________ > X3dom-users mailing list > X3d...@li... > https://lists.sourceforge.net/lists/listinfo/x3dom-users -- Andreas Plesch Waltham, MA 02453 |
From: Timo S. <tim...@th...> - 2023-08-01 12:18:08
|
We are happy to announce the release of X3DOM 1.8.3! This release contains a handful of new features and improvements along with a number of bug fixes since the last release. We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project. * New Features * Add basic support for webXR * Add support for PointProperties * Add support for glTF draco extension * Add support for EXPORT/IMPORT statements * Add bboxDisplay field for X3DBoundedObject and x3dom custom fields bboxMargin and bboxColor * Fixes and Enhancements * Automatic sortType based on auto texture channel count * MovieTexture: autostart, ios and removal * Support url field change for AudioClip * Better indices for textured IFS with creases * Ensure correct children order after ExternProto instancing * Allow smooth creaseAngle during coord updates for IFS * and more... For a detailed list of changes see the changelog on Github: https://github.com/x3dom/x3dom/blob/stable/1.8.x/CHANGELOG.md Release download: https://x3dom.org/download/1.8.3 -- Timo |
From: Joseph D W. <jo...@ea...> - 2023-06-23 22:12:19
|
I’m having trouble thinking there is that aht much ‘wrong’ with that model. I am getting to looking at it in detail, the canonical. Joe From: Brutzman, Donald (Don) (CIV) Sent: Wednesday, June 21, 2023 5:09 PM To: John Carlson; Andreas Plesch; Joe D Williams; Michalis Kamburelis Cc: x3dom mlist; x3dom-developer mlist; Brutzman, Donald (Don) (CIV) Subject: RE: HAnim sample failing in X3DOM, error in view3dscene, additionaltests Diagnostic reports for JinLOA4.x3d, file size 684156 • https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d 1. X3D-Edit checkmark for X3D Validator reports --------- X3D Validator checks commenced for JinLOA4.x3d --------- Performing well-formed XML check... Checking file:/C:/x3d-code/www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d... Well-formed XML check: pass Performing DOCTYPE check... [X3dDoctypeChecker] success: valid XML declaration found.[X3dDoctypeChecker] success: final X3D 4.0 DOCTYPE found. Performing DTD validation... Checking file:/C:/x3d-code/www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d... XML DTD validation: pass Performing X3D schema validation... Checking file:/C:/x3d-code/www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d... Referenced entity at http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd. Referenced entity at http://www.w3.org/2001/XMLSchema.dtd. Referenced entity at http://www.w3.org/2001/datatypes.dtd. XML schema validation: pass Performing X3D regular expression (regex) values check... X3D regex check: complete Performing X3dToX3dvClassicVrmlEncoding.xslt conversion check... Performing X3D Schematron check... X3D version 4.0 is approved by Web3D Consortium and focused on interoperability with HTML5, glTF2.0 Physically Based Rendering (PBR) and Web Audio API, undergoing final administrative review by ISO in 2023. [/X3D, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> version='2.0' with X3D version='4.0' [/X3D/Scene/HAnimHumanoid, diagnostic] ==================================================================================================================== [/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(HAnimJoint) within skeleton hierarchy = 146[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(HAnimSegment) within skeleton hierarchy = 146[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(HAnimSite) within HAnimHumanoid = 0[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(HAnimSite//Viewpoint) within skeleton hierarchy = 0[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(HAnimDisplacer) within skeleton hierarchy = 0[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(<HAnimJoint USE='*' containerField = 'joints'/>) = 146[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(<HAnimSegment USE='*' containerField = 'segments'/>) = 146[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(<HAnimSite USE='*' containerField = 'sites'/>) = 0[/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimHumanoid DEF='hanim_JinLOA4' name='JinLOA4'/> node count(<HAnimSite DEF='*' name ends with '_view'/>) = 0[/X3D/Scene/HAnimHumanoid, diagnostic] ==================================================================================================================== [/X3D/Scene/HAnimHumanoid, diagnostic] <HAnimJoint DEF='hanim_l_tarsal_distal_interphalangeal_1' name='l_tarsal_distal_interphalangeal_1'/> is not a recognized name for HAnim2 HAnimJoint [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[1]/HAnimJoint/HAnimJoint/HAnimJoint[1]/HAnimJoint[1]/HAnimJoint/HAnimJoint/HAnimJoint, warning] <HAnimSegment DEF='hanim_l_tarsal_distal_phalanx_1' name='l_tarsal_distal_phalanx_1'/> has parent HAnimJoint name='l_tarsal_distal_interphalangeal_1' rather than expected parent name='l_tarsal_interphalangeal_1', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[1]/HAnimJoint/HAnimJoint/HAnimJoint[1]/HAnimJoint[1]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimSegment, warning] <HAnimJoint DEF='hanim_r_tarsal_distal_interphalangeal_1' name='r_tarsal_distal_interphalangeal_1'/> is not a recognized name for HAnim2 HAnimJoint [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint[1]/HAnimJoint[1]/HAnimJoint/HAnimJoint/HAnimJoint, warning] <HAnimSegment DEF='hanim_r_tarsal_distal_phalanx_1' name='r_tarsal_distal_phalanx_1'/> has parent HAnimJoint name='r_tarsal_distal_interphalangeal_1' rather than expected parent name='r_tarsal_interphalangeal_1', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint[1]/HAnimJoint[1]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimSegment, warning] <HAnimJoint DEF='hanim_vl5' name='vl5'/> has parent HAnimJoint name='sacroiliac' rather than expected parent name='humanoid_root', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[3], warning] <HAnimJoint DEF='hanim_l_carpometacarpal_5' name='l_carpometacarpal_5'/> has parent HAnimJoint name='l_radiocarpal' rather than expected parent name='l_midcarpal_4_5', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[3]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[5], warning] <HAnimJoint DEF='hanim_r_carpometacarpal_5' name='r_carpometacarpal_5'/> has parent HAnimJoint name='r_radiocarpal' rather than expected parent name='r_midcarpal_4_5', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint/HAnimJoint[3]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[3]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[5], warning] --------- X3D Validator checks complete for JinLOA4.x3d --------- 2. Andreas link to X3DOM Editor • https://andreasplesch.github.io/Library/Viewer/index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d provides following console: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'. x3dom-full.debug.js:65740 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'x') at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged (x3dom-full.debug.js:65740:90) at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12112:19) at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12105:34) at NodeList.forEach (<anonymous>) at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12103:36) at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12105:34) at NodeList.forEach (<anonymous>) at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12103:36) at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12105:34) at NodeList.forEach (<anonymous>) nodeChanged @ x3dom-full.debug.js:65740 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12112 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 (anonymous) @ x3dom-full.debug.js:12105 x3dom.NodeNameSpace.setupTree @ x3dom-full.debug.js:12103 x3dom.X3DDocument._setup @ x3dom-full.debug.js:21793 next_step @ x3dom-full.debug.js:21731 next_step @ x3dom-full.debug.js:21743 x3dom.X3DDocument.load @ x3dom-full.debug.js:21747 x3dom.X3DCanvas.load @ x3dom-full.debug.js:2121 onload @ x3dom-full.debug.js:20366 x3dom.reload @ x3dom-full.debug.js:20429 x3dom.Runtime.replaceWorld @ x3dom-full.debug.js:20043 updatex3d @ index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d:228 load @ index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d:214 3. am getting similar browser console error if launched directly in X3DOM • https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4X3dom.xhtml 4. view3dscene (launched from X3D-Edit) reports Suggestion: add a button to view3dscene diagnostic that enables user to “Copy to clipboard” – usually this is provided. Closing the X3DOM editor did not fix this access problem. Closing the X3D-Edit pane for this problem did not fix this access problem, but closing X3D-Edit executable (surprisingly) did. Not sure why, will look further at that. Now view3dscene renders the model and provides 11 warnings: 11 warnings: X3D: Unknown X3D field name (unhandled X3D XML attribute) "loa" in node "HAnimHumanoid" X3D: Error when reading MFString field "value" value. Possibly missing double quotes (treating as a single string): Error at line 1 column 4: Expected string, got "Jin" X3D: Error when reading MFString field "value" value. Possibly missing double quotes (treating as a single string): Error at line 1 column 19: Expected string, got "myeongwonlee@gmail" X3D: X3D XML: More than one value specified for SFNode field MetadataSet.metadata X3D: Error when reading MFString field "value" value. Possibly missing double quotes (treating as a single string): Error at line 1 column 3: Expected string, got integer 31 X3D: X3D XML: More than one value specified for SFNode field MetadataSet.metadata X3D: Error when reading MFString field "value" value. Possibly missing double quotes (treating as a single string): Error at line 1 column 7: Expected string, got "female" X3D: X3D XML: More than one value specified for SFNode field MetadataSet.metadata X3D: X3D XML: More than one value specified for SFNode field MetadataSet.metadata X3D: X3D XML: More than one value specified for SFNode field MetadataSet.metadata X3D: Invalid index for field TextureCoordinate.point (MFVec2f) Scene URL: file:///C:/x3d-code/www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d. Use "File->View Warnings" menu to view these warnings again. 5. Testing in X_ITE: renders fine, shows no errors in console. • https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4X_ITE.html 6. Xj3D has a verbose console without any errors apparent, However only renders a black screen. 7. Xj3D Xj3dVersionInformation: v2.3-nps utilizing NPS Open DIS v7 with 3D rendering by ----------------------------------------------------------------------------------------------------- Package: org.j3d.aviatrix3d Extension Name: org.j3d.aviatrix3d Specification Title: Aviatrix3D 3.1.1-nps - NPS SF Specification Vendor: Justin Couch Specification Version: 3.1.1 Implementation Title: Aviatrix3D 3.1.1-nps - NPS SF Implementation Vendor: Savage Research Group (SRG) of the Modeling, Virtual Environments and Simulation (MOVES) Institute at the Naval Postgraduate School (NPS), Monterey, CA Implementation Vendor ID: edu.nps.moves Implementation URL: https://svn.code.sf.net/p/xj3d/code/branches/Supporting_APIs/aviatrix3d Implementation Version: 3.1.1-nps built on Fri, 26 May 2023 1434 -0700 Implementation Build: 3.1.1-nps Implementation Branch: branches/Supporting_APIs/aviatrix3d Implementation Commit: 12701 Implementation SHA Sources: null Implementation SHA Classes: null Implementation SHA Classes-this: null Implementation SHA Natives: null Implementation SHA Natives-this: null ----------------------------------------------------------------------------------------------------- on top of ----------------------------------------------------------------------------------------------------- Package: com.jogamp Extension Name: com.jogamp Specification Title: JogAmp Java Bindings Specification Specification Vendor: JogAmp Community Specification Version: 2.5 Implementation Title: JogAmp Java Bindings Fat Jar Implementation Vendor: JogAmp Community Implementation Vendor ID: com.jogamp Implementation URL: http://jogamp.org/ Implementation Version: 2.5.0-rc-20230515 Implementation Build: 2.5-b957-20230515 Implementation Branch: origin/master Implementation Commit: 9301bf1854d91405319801b62c268e2ca09406e6 Implementation SHA Sources: null Implementation SHA Classes: null Implementation SHA Classes-this: null Implementation SHA Natives: null Implementation SHA Natives-this: null ----------------------------------------------------------------------------------------------------- Operating system: Windows 10 10.0 Java environment: Oracle Corporation 20.0.1 BuildStamp time and date: 1436 on May 26 2023 Initializing OpenGL X3D browser in GLCanvas (AWT) mode. Graphics architecture will support 16 samples of full screen antialiasing. Warning: Native image loading unavailable, using default. 8. Not seeing any texture coordinate arithmetic problems. There is probably a rule in X3D Schematron (within X3D Validator) to test for that. Recommend checking further and we can define/implement further validation rules as needed. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br bru...@np... Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, navy robotics https://faculty.nps.edu/brutzman From: John Carlson <yot...@gm...> Sent: Wednesday, June 21, 2023 2:25 PM To: Andreas Plesch <and...@gm...>; Brutzman, Donald (Don) (CIV) <bru...@np...>; Joe D Williams <jo...@ea...> Cc: Michalis Kamburelis <mic...@gm...>; x3dom mlist <x3d...@li...>; x3dom-developer mlist <x3d...@li...> Subject: Re: HAnim sample failing in X3DOM, error in view3dscene. Yes, good analysis Andreas and Michalis, I concluded the same thing. I understand that i can bisect the file…easier said than done. What i can do is write a program to find the bug and then extend output model with a key phrase in the TextureCoordinate point field. That will be easier that searching by hand. I suggest a change to the x3d validator. John On Wed, Jun 21, 2023 at 10:45 AM Andreas Plesch <and...@gm...> wrote: I agree with Michalis' analysis and also remember a similar discussion, I think with regards to Joe's kick model. https://andreasplesch.github.io/Library/Viewer/index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d lets you edit the xml interactively and perhaps can aid in finding the missing tex. coords. Cheers, Andreas On Wed, Jun 21, 2023 at 10:43 AM Michalis Kamburelis <mic...@gm...> wrote: There are not enough texture coordinates specified. The X3D model isn't valid. (We talked about this on x3d-public already some time ago, see thread "[x3d-public] New description fields".) Details: - Renderer doesn't have enough information what texture coordinate to assign to some vertexes. (And there's no reasonable fallback, e.g. "use last texture coordinate" wouldn't make sense -- that's not a useful thing to do with texture coordinates, at least in general models it wouldn't make sense, better to ask user to provide all texture coordinates.) - Spec: https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/geometry3D.html#IndexedFaceSet , texts like - """If the greatest index in the texCoordIndex field is N, then there shall be N+1 texture coordinates in the X3DTextureCoordinateNode.""" - """If the greatest index in the coordIndex field is N, then there shall be N+1 texture coordinates in the X3DTextureCoordinateNode node.""" I improved the view3dscene error message to say: X3D: Invalid index 44 (should be less than count 44) for field TextureCoordinate.point (type: MFVec2f) To pinpoint it (as I see there are many TextureCoodinate nodes), you can bisect the model (cut away this or that half, and see when it stops failing), or assign names to X3D names to pinpoint it, i.e. edit X3D to change <TextureCoordinate ... -> <TextureCoordinate DEF="something unique" ... Unfortunately in view3dscene we don't have at that point knowledge about exact line number from XML file -- I know, it would be useful in this case, to say "the problem is at TextureCoordinate at line 123 in X3D XML". Regards, Michalis śr., 21 cze 2023 o 15:15 John Carlson <yot...@gm...> napisał(a): I'm having issues with the attached file in X3DOM. Thanks for any assistance! Here's what the errors show in view3dscene: x3dom-full.debug.js:65877 Uncaught TypeError: Cannot read properties of undefined (reading 'x') at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged (x3dom-full.debug.js:65877:90) at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12167:19) at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) at NodeList.forEach (<anonymous>) at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) at NodeList.forEach (<anonymous>) at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) at NodeList.forEach (<anonymous>) -- Andreas Plesch Waltham, MA 02453 |
From: John C. <yot...@gm...> - 2023-06-21 22:25:22
|
Here's the HAnimSegment in question: <HAnimSegment DEF='hanim_r_carpal_proximal_phalanx_1' name='r_carpal_proximal_phalanx_1'> <Transform translation='-8.029 29.900 1.590'> <Shape> <Appearance> <Material diffuseColor='0.588 0.588 0.588'/> <ImageTexture USE='JinLOA4TextureAtlas'/> </Appearance> <IndexedFaceSet coordIndex='5 6 0 -1 7 3 14 -1 14 13 7 -1 5 0 17 -1 17 10 5 -1 4 5 10 -1 10 9 4 -1 3 4 9 -1 9 14 3 -1 0 1 19 -1 19 17 0 -1 1 7 13 -1 13 19 1 -1 1 0 2 -1 0 6 8 -1 8 2 0 -1 9 10 11 -1 11 12 9 -1 13 14 15 -1 15 16 13 -1 10 17 18 -1 18 11 10 -1 19 13 16 -1 16 20 19 -1 17 19 20 -1 20 18 17 -1 14 9 12 -1 12 15 14 -1 15 12 20 -1 20 16 15 -1 11 18 20 -1 20 12 11 -1 22 23 24 -1 24 25 26 -1 22 24 26 -1 21 22 26 -1 28 29 30 -1 30 27 28 -1 8 6 22 -1 22 21 8 -1 6 5 23 -1 23 22 6 -1 5 4 24 -1 24 23 5 -1 4 3 25 -1 25 24 4 -1 3 7 26 -1 26 25 3 -1 27 30 31 -1 31 32 27 -1 7 1 28 -1 28 27 7 -1 1 2 29 -1 29 28 1 -1 2 8 30 -1 30 29 2 -1 8 21 31 -1 31 30 8 -1 21 26 32 -1 32 31 21 -1 26 7 27 -1 27 32 26 -1' creaseAngle='3.14159' texCoordIndex='0 1 2 -1 36 33 34 -1 34 35 36 -1 0 2 7 -1 7 8 0 -1 10 0 8 -1 8 9 10 -1 33 38 37 -1 37 34 33 -1 2 11 12 -1 12 7 2 -1 39 36 35 -1 35 40 39 -1 11 2 13 -1 2 1 14 -1 14 13 2 -1 9 8 15 -1 15 16 9 -1 5 4 17 -1 17 18 5 -1 8 7 19 -1 19 15 8 -1 12 5 18 -1 18 20 12 -1 7 12 20 -1 20 19 7 -1 4 9 16 -1 16 17 4 -1 17 16 20 -1 20 18 17 -1 15 19 20 -1 20 16 15 -1 22 23 24 -1 24 25 26 -1 22 24 26 -1 21 22 26 -1 28 29 30 -1 30 27 28 -1 14 1 22 -1 22 21 14 -1 1 0 23 -1 23 22 1 -1 0 10 24 -1 24 23 0 -1 10 3 25 -1 25 24 10 -1 33 36 42 -1 42 41 33 -1 27 30 31 -1 31 32 27 -1 6 11 28 -1 28 27 6 -1 11 13 29 -1 29 28 11 -1 13 14 30 -1 30 29 13 -1 14 21 31 -1 31 30 14 -1 21 26 32 -1 32 31 21 -1 42 36 43 -1 43 44 42 -1'> <Coordinate point='-0.6480 -0.1572 -0.1816 -0.2215 -0.4696 -0.3727 -0.7293 -0.3514 -0.3769 0.5989 0.0674 -0.0620 0.3258 0.2652 0.2094 -0.3575 0.3782 0.3089 -0.6921 -0.0248 -0.2768 0.3898 -0.3658 -0.5188 -0.7948 -0.1175 -0.4637 0.2134 -0.6161 0.8058 -0.3101 -0.4028 0.7384 -0.1954 -0.8397 0.9419 0.1104 -0.9591 0.8926 0.2493 -1.1510 0.2193 0.5111 -0.8320 0.6281 0.3686 -0.9810 0.7131 0.1898 -1.2270 0.3830 -0.5399 -0.7980 0.2786 -0.4043 -1.1270 0.5533 -0.1346 -1.1160 0.1902 -0.1035 -1.2540 0.4943 -0.4370 0.1054 -0.5720 -0.4429 0.1652 -0.5023 -0.1619 0.4787 -0.0154 0.2164 0.3980 -0.0699 0.3666 0.2424 -0.3170 0.2404 0.0654 -0.5934 0.2919 -0.3931 -0.7578 -0.1692 -0.5049 -0.6608 -0.5909 -0.3962 -0.6566 -0.6389 -0.2511 -0.7092 -0.4111 -0.0844 -0.8017 0.1733 -0.1282 -0.8504'/> <TextureCoordinate point='0.8786 0.0507 0.8570 0.0621 0.8601 0.0649 0.8670 0.0598 0.8887 0.0786 0.8747 0.0865 0.8533 0.0697 0.8760 0.0783 0.8930 0.0688 0.8992 0.0702 0.8819 0.0483 0.8561 0.0728 0.8736 0.0851 0.8532 0.0697 0.8503 0.0646 0.8986 0.0785 0.8970 0.0809 0.8914 0.0813 0.8802 0.0861 0.8841 0.0856 0.8821 0.0883 0.8487 0.0595 0.8509 0.0581 0.8683 0.0489 0.8680 0.0507 0.8608 0.0544 0.8505 0.0603 0.8455 0.0706 0.8468 0.0730 0.8455 0.0707 0.8437 0.0676 0.8416 0.0639 0.8422 0.0648 0.8729 0.2464 0.8482 0.2317 0.8612 0.2211 0.8847 0.2342 0.8433 0.2381 0.8632 0.2548 0.8814 0.2316 0.8625 0.2222 0.8799 0.2506 0.8891 0.2430 0.8922 0.2320'/> </IndexedFaceSet> </Shape> </Transform> </HAnimSegment> Thanks for the example that showed a bug in my scaling JavaScript code, Joe, most helpful! I wasn't going through the point array at all because I was using len instead of length (type-safety would have caught this). I know this has been months and months. On Wed, Jun 21, 2023 at 4:24 PM John Carlson <yot...@gm...> wrote: > Yes, good analysis Andreas and Michalis, I concluded the same thing. I > understand that i can bisect the file…easier said than done. What i can do > is write a program to find the bug and then extend output model with a key > phrase in the TextureCoordinate point field. That will be easier that > searching by hand. > > I suggest a change to the x3d validator. > > John > > On Wed, Jun 21, 2023 at 10:45 AM Andreas Plesch <and...@gm...> > wrote: > >> I agree with Michalis' analysis and also remember a similar discussion, I >> think with regards to Joe's kick model. >> >> >> https://andreasplesch.github.io/Library/Viewer/index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d >> >> lets you edit the xml interactively and perhaps can aid in finding the >> missing tex. coords. >> >> Cheers, Andreas >> >> On Wed, Jun 21, 2023 at 10:43 AM Michalis Kamburelis < >> mic...@gm...> wrote: >> >>> There are not enough texture coordinates specified. The X3D model isn't >>> valid. >>> >>> (We talked about this on x3d-public already some time ago, see thread >>> "[x3d-public] New description fields".) >>> >>> Details: >>> >>> - Renderer doesn't have enough information what texture coordinate to >>> assign to some vertexes. (And there's no reasonable fallback, e.g. "use >>> last texture coordinate" wouldn't make sense -- that's not a useful thing >>> to do with texture coordinates, at least in general models it wouldn't make >>> sense, better to ask user to provide all texture coordinates.) >>> >>> - Spec: >>> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/geometry3D.html#IndexedFaceSet >>> , texts like >>> >>> - """If the greatest index in the texCoordIndex field is N, then >>> there shall be N+1 texture coordinates in the X3DTextureCoordinateNode.""" >>> >>> - """If the greatest index in the coordIndex field is N, then there >>> shall be N+1 texture coordinates in the X3DTextureCoordinateNode node.""" >>> >>> I improved the view3dscene error message to say: >>> >>> X3D: Invalid index 44 (should be less than count 44) for field >>> TextureCoordinate.point (type: MFVec2f) >>> >>> To pinpoint it (as I see there are many TextureCoodinate nodes), you can >>> bisect the model (cut away this or that half, and see when it stops >>> failing), or assign names to X3D names to pinpoint it, i.e. edit X3D to >>> change >>> >>> <TextureCoordinate ... >>> >>> -> >>> >>> <TextureCoordinate DEF="something unique" ... >>> >>> Unfortunately in view3dscene we don't have at that point knowledge about >>> exact line number from XML file -- I know, it would be useful in this case, >>> to say "the problem is at TextureCoordinate at line 123 in X3D XML". >>> >>> Regards, >>> Michalis >>> >>> >>> śr., 21 cze 2023 o 15:15 John Carlson <yot...@gm...> napisał(a): >>> >>>> I'm having issues with the attached file in X3DOM. Thanks for any >>>> assistance! >>>> >>>> Here's what the errors show in view3dscene: >>>> >>>> [image: image.png] >>>> >>>> x3dom-full.debug.js:65877 Uncaught TypeError: Cannot read properties >>>> of undefined (reading 'x') >>>> at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged >>>> (x3dom-full.debug.js:65877:90) >>>> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12167:19) >>>> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >>>> at NodeList.forEach (<anonymous>) >>>> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) >>>> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >>>> at NodeList.forEach (<anonymous>) >>>> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) >>>> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >>>> at NodeList.forEach (<anonymous>) >>>> >>> >> >> -- >> Andreas Plesch >> Waltham, MA 02453 >> > |
From: John C. <yot...@gm...> - 2023-06-21 21:25:15
|
Yes, good analysis Andreas and Michalis, I concluded the same thing. I understand that i can bisect the file…easier said than done. What i can do is write a program to find the bug and then extend output model with a key phrase in the TextureCoordinate point field. That will be easier that searching by hand. I suggest a change to the x3d validator. John On Wed, Jun 21, 2023 at 10:45 AM Andreas Plesch <and...@gm...> wrote: > I agree with Michalis' analysis and also remember a similar discussion, I > think with regards to Joe's kick model. > > > https://andreasplesch.github.io/Library/Viewer/index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d > > lets you edit the xml interactively and perhaps can aid in finding the > missing tex. coords. > > Cheers, Andreas > > On Wed, Jun 21, 2023 at 10:43 AM Michalis Kamburelis < > mic...@gm...> wrote: > >> There are not enough texture coordinates specified. The X3D model isn't >> valid. >> >> (We talked about this on x3d-public already some time ago, see thread >> "[x3d-public] New description fields".) >> >> Details: >> >> - Renderer doesn't have enough information what texture coordinate to >> assign to some vertexes. (And there's no reasonable fallback, e.g. "use >> last texture coordinate" wouldn't make sense -- that's not a useful thing >> to do with texture coordinates, at least in general models it wouldn't make >> sense, better to ask user to provide all texture coordinates.) >> >> - Spec: >> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/geometry3D.html#IndexedFaceSet >> , texts like >> >> - """If the greatest index in the texCoordIndex field is N, then >> there shall be N+1 texture coordinates in the X3DTextureCoordinateNode.""" >> >> - """If the greatest index in the coordIndex field is N, then there >> shall be N+1 texture coordinates in the X3DTextureCoordinateNode node.""" >> >> I improved the view3dscene error message to say: >> >> X3D: Invalid index 44 (should be less than count 44) for field >> TextureCoordinate.point (type: MFVec2f) >> >> To pinpoint it (as I see there are many TextureCoodinate nodes), you can >> bisect the model (cut away this or that half, and see when it stops >> failing), or assign names to X3D names to pinpoint it, i.e. edit X3D to >> change >> >> <TextureCoordinate ... >> >> -> >> >> <TextureCoordinate DEF="something unique" ... >> >> Unfortunately in view3dscene we don't have at that point knowledge about >> exact line number from XML file -- I know, it would be useful in this case, >> to say "the problem is at TextureCoordinate at line 123 in X3D XML". >> >> Regards, >> Michalis >> >> >> śr., 21 cze 2023 o 15:15 John Carlson <yot...@gm...> napisał(a): >> >>> I'm having issues with the attached file in X3DOM. Thanks for any >>> assistance! >>> >>> Here's what the errors show in view3dscene: >>> >>> [image: image.png] >>> >>> x3dom-full.debug.js:65877 Uncaught TypeError: Cannot read properties of >>> undefined (reading 'x') >>> at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged >>> (x3dom-full.debug.js:65877:90) >>> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12167:19) >>> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >>> at NodeList.forEach (<anonymous>) >>> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) >>> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >>> at NodeList.forEach (<anonymous>) >>> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) >>> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >>> at NodeList.forEach (<anonymous>) >>> >> > > -- > Andreas Plesch > Waltham, MA 02453 > |
From: Andreas P. <and...@gm...> - 2023-06-21 15:45:10
|
I agree with Michalis' analysis and also remember a similar discussion, I think with regards to Joe's kick model. https://andreasplesch.github.io/Library/Viewer/index.html?url=https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4.x3d lets you edit the xml interactively and perhaps can aid in finding the missing tex. coords. Cheers, Andreas On Wed, Jun 21, 2023 at 10:43 AM Michalis Kamburelis < mic...@gm...> wrote: > There are not enough texture coordinates specified. The X3D model isn't > valid. > > (We talked about this on x3d-public already some time ago, see thread > "[x3d-public] New description fields".) > > Details: > > - Renderer doesn't have enough information what texture coordinate to > assign to some vertexes. (And there's no reasonable fallback, e.g. "use > last texture coordinate" wouldn't make sense -- that's not a useful thing > to do with texture coordinates, at least in general models it wouldn't make > sense, better to ask user to provide all texture coordinates.) > > - Spec: > https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/geometry3D.html#IndexedFaceSet > , texts like > > - """If the greatest index in the texCoordIndex field is N, then there > shall be N+1 texture coordinates in the X3DTextureCoordinateNode.""" > > - """If the greatest index in the coordIndex field is N, then there > shall be N+1 texture coordinates in the X3DTextureCoordinateNode node.""" > > I improved the view3dscene error message to say: > > X3D: Invalid index 44 (should be less than count 44) for field > TextureCoordinate.point (type: MFVec2f) > > To pinpoint it (as I see there are many TextureCoodinate nodes), you can > bisect the model (cut away this or that half, and see when it stops > failing), or assign names to X3D names to pinpoint it, i.e. edit X3D to > change > > <TextureCoordinate ... > > -> > > <TextureCoordinate DEF="something unique" ... > > Unfortunately in view3dscene we don't have at that point knowledge about > exact line number from XML file -- I know, it would be useful in this case, > to say "the problem is at TextureCoordinate at line 123 in X3D XML". > > Regards, > Michalis > > > śr., 21 cze 2023 o 15:15 John Carlson <yot...@gm...> napisał(a): > >> I'm having issues with the attached file in X3DOM. Thanks for any >> assistance! >> >> Here's what the errors show in view3dscene: >> >> [image: image.png] >> >> x3dom-full.debug.js:65877 Uncaught TypeError: Cannot read properties of >> undefined (reading 'x') >> at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged >> (x3dom-full.debug.js:65877:90) >> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12167:19) >> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >> at NodeList.forEach (<anonymous>) >> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) >> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >> at NodeList.forEach (<anonymous>) >> at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) >> at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) >> at NodeList.forEach (<anonymous>) >> > -- Andreas Plesch Waltham, MA 02453 |
From: Michalis K. <mic...@gm...> - 2023-06-21 14:43:42
|
There are not enough texture coordinates specified. The X3D model isn't valid. (We talked about this on x3d-public already some time ago, see thread "[x3d-public] New description fields".) Details: - Renderer doesn't have enough information what texture coordinate to assign to some vertexes. (And there's no reasonable fallback, e.g. "use last texture coordinate" wouldn't make sense -- that's not a useful thing to do with texture coordinates, at least in general models it wouldn't make sense, better to ask user to provide all texture coordinates.) - Spec: https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/geometry3D.html#IndexedFaceSet , texts like - """If the greatest index in the texCoordIndex field is N, then there shall be N+1 texture coordinates in the X3DTextureCoordinateNode.""" - """If the greatest index in the coordIndex field is N, then there shall be N+1 texture coordinates in the X3DTextureCoordinateNode node.""" I improved the view3dscene error message to say: X3D: Invalid index 44 (should be less than count 44) for field TextureCoordinate.point (type: MFVec2f) To pinpoint it (as I see there are many TextureCoodinate nodes), you can bisect the model (cut away this or that half, and see when it stops failing), or assign names to X3D names to pinpoint it, i.e. edit X3D to change <TextureCoordinate ... -> <TextureCoordinate DEF="something unique" ... Unfortunately in view3dscene we don't have at that point knowledge about exact line number from XML file -- I know, it would be useful in this case, to say "the problem is at TextureCoordinate at line 123 in X3D XML". Regards, Michalis śr., 21 cze 2023 o 15:15 John Carlson <yot...@gm...> napisał(a): > I'm having issues with the attached file in X3DOM. Thanks for any > assistance! > > Here's what the errors show in view3dscene: > > [image: image.png] > > x3dom-full.debug.js:65877 Uncaught TypeError: Cannot read properties of > undefined (reading 'x') > at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged > (x3dom-full.debug.js:65877:90) > at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12167:19) > at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) > at NodeList.forEach (<anonymous>) > at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) > at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) > at NodeList.forEach (<anonymous>) > at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:12158:36) > at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:12160:34) > at NodeList.forEach (<anonymous>) > |
From: Web3D 2. <web...@vi...> - 2023-05-26 09:20:22
|
The final deadline for submissions of Papers is June 15, 2023 *The Web3D 2023 Papers Submission Deadline is Approaching!* Don't miss your chance to shape the future of 3D Graphics. The final deadline for submissions of Papers <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=194c884236&e=f0f523551e> to the annual Web3D 2023 Conference <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=90baef15eb&e=f0f523551e> on 9-11 October 2023 in beautiful San Sebastián, Spain is looming - *June 15, 2023*. Important Dates <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=80e2775118&e=f0f523551e> This Conference is sponsored by ACM SIGGRAPH <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=c45c79a495&e=f0f523551e>, in cooperation with Web3D Consortium <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=83867697af&e=f0f523551e> and supported by Eurographics <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=b4c5face78&e=f0f523551e>, *and is hosted by Vicomtech <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=599e355fdb&e=f0f523551e> Spain.* We Welcome Submissions in the Following Categories: 1. Academic Papers and Posters 2. Tutorials 3. Workshops 4. Industrial Use Cases 5. Competition Entries Why Submit your Work? - *Visibility*: Gain exposure to an international audience passionate about 3D Graphics. - *Networking*: Engage with leading minds in your industry. - *Influence*: Drive the conversation and inspire the next generation of creators and innovators. - *Publication Possibility*: Open the doors to new opportunities with your published work. Ready to make an impact? Submit your paper here <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=aff5d25a3b&e=f0f523551e> by June 15, 2023 Accepted papers and poster summaries will be published in the Web3D 2023 ACM Conference Proceedings, available in the ACM Digital Library <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=a6e56dc6f3&e=f0f523551e>. Works selected for the Best Paper awards will be invited to submit extended versions to the Computers & Graphics journal <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=c3c194426a&e=f0f523551e> . Learn More <https://web3d.us10.list-manage.com/track/click?u=0051673b83909ae284624feb2&id=a5525e4472&e=f0f523551e> |
From: Web3D 2. <web...@vi...> - 2023-03-20 11:04:03
|
*9-11 October 2023 - Call for Papers and Contributions - **Submission deadline 15 June 2023* *Call for Papers <https://web3d.siggraph.org/cfp/> and **Submission Details <https://easychair.org/my/conference?conf=web3d2023> * Join your fellow 3D technologists and peers by contributing your scientific innovation, technical development or artistic accomplishments! We welcome all topics related to Web/mobile 3D content creation, publishing technology, tools, Virtual worlds, Metaverse and related studies. Share your latest 3D work! The 28th *Web3D 2023 Conference <https://web3d.siggraph.org/>* on 3D Web Technology will be hosted by Vicomtech <https://www.vicomtech.org/en> <http://vicomtech.org>in San Sebastian, Spain from *9-11 October 2023*. Sponsored by ACM SIGGRAPH <http://www.acm.org/> in cooperation with the Web3D Consortium <http://www.web3d.org/>. This year's theme is "*Towards inter-connectivity of Metaverses*" *Topics and areas of interest:* We welcome all topics related to Web/mobile 3D content creation, immersive realities, 3D compression, publishing technology, tools, and related studies. - VR/AR/MR/XR: virtual, augmented, mixed, cross and extended realities - Novel interactive 3D web applications in all areas and sectors such as entertainment, education, training, cultural heritage and tourism, digital twins, medicine, military, smart-manufacturing / industry 4.0, information & data visualization, science, geographic information systems, digital globes, subsurface exploration and mining, integrated marine data management and visualization, smart city, building information modeling, and architecture. - HTML5 3D, WebGL, WebGPU, glTF, MPEG and other languages and formats that support the 3D Web - Semantic Web for 3D objects and scenes - X3D application examples - Novel APIs, toolkits, and frameworks for 3D web and associated application domains - 3D content creation and modeling, 3D content scanning, reconstruction, compression, printing, visualization - Artificial Intelligence (AI) technologies for 3D processing and its various use cases - Algorithms for shape modeling, optimization, analysis, and processing - 3D technologies for Digital humans - 3D technologies for Medical and Health Data - Digital Twins on the Web: modeling, cinematics, photorealism, simulation, etc. - User-centered applications: usability, ergonomics, speed and responsiveness, customization of the virtual experience - Visual analytics to enhance understability of large data in virtual environments - Cloud-based rendering, services, interoperability for large-scale models, animations, virtual worlds and metaverses - End to end systems for streaming, compression, and transmission of 3D content - Motion capture for composition and streaming of behaviors and expressions - Multi-modal 3D interaction paradigms, including spatial UI, gesture and voice - Diffusion and adoption of 3D Web technologies, comparative studies, historical perspectives, www integration - Mobile 3D applications and usability studies, including navigation performance and immersion Impact. - Metaverse in education and its impact on learning outcomes. - Metaverse in digital legacy and its impact on tourism. - Metaverse in entertainment and its impact on traditional media. - Metaverse for training and simulation in various industries. - The impact of the Metaverse on speech, communication, interaction, and physical spaces. The accepted papers and poster summaries will be published in the Web3D 2023 ACM Conference Proceedings, available in the ACM Digital Library. Works selected for the Best Paper awards will be invited to submit extended versions to a selection of specialized journals For questions about the program and conference topics please email us at: pro...@we... |
From: Batagelj, V. <vla...@fm...> - 2023-01-18 02:43:41
|
Dear Andreas, Thanks again. I updated the page http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline with your last info. I also drilled into the structure of the European airports main core http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircores . I think that we have now a relatively simple and operational option for inspecting info about objects in 3D scenes (networks, data points, objects on a map, ...). This is a very useful option for 3D visualizations in data analysis. best, Vlado Vladimir Batagelj<http://vladowiki.fmf.uni-lj.si/doku.php?id=vb> ________________________________ From: Andreas Plesch <and...@gm...> Sent: Tuesday, January 17, 2023 2:49 PM To: Batagelj, Vladimir <vla...@fm...> Cc: x3d...@li... <x3d...@li...> Subject: Re: [x3dom-developers] Anchor description Hi Vlado, Anchor descriptions should be available also in x3dom.js for the latest dev version. Thanks, Andreas On Mon, Jan 16, 2023 at 8:59 PM Batagelj, Vladimir <vla...@fm...> wrote: > > Dear Andreas, > > thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom > a page with the scene included from another file using <Inline> > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline > and an example of its application in 3D data visualization > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore > > It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm...> > Sent: Monday, January 16, 2023 12:49 AM > To: Batagelj, Vladimir <vla...@fm...> > Cc: x3d...@li... <x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description > > Hi Vlado, > > Super. Please feel free to share any interesting results, perhaps of > networks, on x3dom-developers, x3dom-users or the x3d-public mailing > lists. > > I added the description field value to the log output in the latest > dev version, and fixed Anchor behaviour for empty urls as it is > explicitly specified. > > You may be interested in the x3d python package > (https://pypi.org/project/x3d/) which helps with generating conforming > x3d output. > > Best regards, Andreas > > On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir > <vla...@fm...> wrote: > > > > Dear Andreas, > > > > thank you very much for your help. Your solution is what I was searching for. > > Yes, it is a good idea to add the description to the log message. > > > > best regards, Vlado > > > > Vladimir Batagelj > > > > > > ________________________________ > > From: Andreas Plesch <and...@gm...> > > Sent: Sunday, January 15, 2023 5:51 AM > > To: Batagelj, Vladimir <vla...@fm...> > > Cc: x3d...@li... <x3d...@li...> > > Subject: Re: [x3dom-developers] Anchor description > > > > Hi Vladimir, > > > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > > has the standard specification of the Anchor node. It is mostly used > > with an URL to load other content. > > > > How the description field is used varies from browser to browser. > > x3dom shows a message in the debug log ("d" key) but it does not > > currently include the description. It is probably a good idea to add > > the description to the log message in an update. > > > > If you want to stay with an X3D only solution, you could use a > > TouchSensor and route the description field to a Text node, in some > > way. > > > > But it sounds like you are considering a javascript/HTML solution. You > > would need to know a little bit about HTML/DOM and javascript. > > > > Ok, I put together a codepen which shows one way to listen to a click > > event on an Anchor and then use the description on the web page: > > > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 > > > > It follows more or less the example you found but without jquery and a > > bit simpler. Take a look, > > > > Cheers, Andreas > > > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > > <vla...@fm...> wrote: > > > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > > > How can I achieve this in X3DOM ? > > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html says > > > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html, which is very close to the solution of my problem. I tried to adapt it without success. > > > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > > > best, > > > > > > Vladimir Batagelj > > > > > > > > > _______________________________________________ > > > x3dom-developers mailing list > > > x3d...@li... > > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers > > > > > > > > -- > > Andreas Plesch > > Waltham, MA 02453 > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Andreas P. <and...@gm...> - 2023-01-17 13:49:24
|
Hi Vlado, Anchor descriptions should be available also in x3dom.js for the latest dev version. Thanks, Andreas On Mon, Jan 16, 2023 at 8:59 PM Batagelj, Vladimir <vla...@fm...> wrote: > > Dear Andreas, > > thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom > a page with the scene included from another file using <Inline> > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline > and an example of its application in 3D data visualization > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore > > It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm...> > Sent: Monday, January 16, 2023 12:49 AM > To: Batagelj, Vladimir <vla...@fm...> > Cc: x3d...@li... <x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description > > Hi Vlado, > > Super. Please feel free to share any interesting results, perhaps of > networks, on x3dom-developers, x3dom-users or the x3d-public mailing > lists. > > I added the description field value to the log output in the latest > dev version, and fixed Anchor behaviour for empty urls as it is > explicitly specified. > > You may be interested in the x3d python package > (https://pypi.org/project/x3d/) which helps with generating conforming > x3d output. > > Best regards, Andreas > > On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir > <vla...@fm...> wrote: > > > > Dear Andreas, > > > > thank you very much for your help. Your solution is what I was searching for. > > Yes, it is a good idea to add the description to the log message. > > > > best regards, Vlado > > > > Vladimir Batagelj > > > > > > ________________________________ > > From: Andreas Plesch <and...@gm...> > > Sent: Sunday, January 15, 2023 5:51 AM > > To: Batagelj, Vladimir <vla...@fm...> > > Cc: x3d...@li... <x3d...@li...> > > Subject: Re: [x3dom-developers] Anchor description > > > > Hi Vladimir, > > > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > > has the standard specification of the Anchor node. It is mostly used > > with an URL to load other content. > > > > How the description field is used varies from browser to browser. > > x3dom shows a message in the debug log ("d" key) but it does not > > currently include the description. It is probably a good idea to add > > the description to the log message in an update. > > > > If you want to stay with an X3D only solution, you could use a > > TouchSensor and route the description field to a Text node, in some > > way. > > > > But it sounds like you are considering a javascript/HTML solution. You > > would need to know a little bit about HTML/DOM and javascript. > > > > Ok, I put together a codepen which shows one way to listen to a click > > event on an Anchor and then use the description on the web page: > > > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 > > > > It follows more or less the example you found but without jquery and a > > bit simpler. Take a look, > > > > Cheers, Andreas > > > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > > <vla...@fm...> wrote: > > > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > > > How can I achieve this in X3DOM ? > > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html says > > > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html, which is very close to the solution of my problem. I tried to adapt it without success. > > > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > > > best, > > > > > > Vladimir Batagelj > > > > > > > > > _______________________________________________ > > > x3dom-developers mailing list > > > x3d...@li... > > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers > > > > > > > > -- > > Andreas Plesch > > Waltham, MA 02453 > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Andreas P. <and...@gm...> - 2023-01-17 13:43:54
|
Hi Valdo, On Mon, Jan 16, 2023 at 8:59 PM Batagelj, Vladimir <vla...@fm...> wrote: > > Dear Andreas, > > thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom > a page with the scene included from another file using <Inline> > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline > and an example of its application in 3D data visualization > http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore > > It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . There is this error message in the console: Refused to execute inline script because it violates the following Content Security Policy directive: "default-src 'self' https://*". Either the 'unsafe-inline' keyword, a hash ('sha256-R5a29waRh/UcgfGNNsOEughkTCufhjckKO8svocjcNw='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'script-src' was not explicitly set, so 'default-src' is used as a fallback. When you remove the meta statement with the content security policy, it works. <meta http-equiv="Content-Security-Policy" content="default-src 'self' https://*;"> Hope this helps, Andreas > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm...> > Sent: Monday, January 16, 2023 12:49 AM > To: Batagelj, Vladimir <vla...@fm...> > Cc: x3d...@li... <x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description > > Hi Vlado, > > Super. Please feel free to share any interesting results, perhaps of > networks, on x3dom-developers, x3dom-users or the x3d-public mailing > lists. > > I added the description field value to the log output in the latest > dev version, and fixed Anchor behaviour for empty urls as it is > explicitly specified. > > You may be interested in the x3d python package > (https://pypi.org/project/x3d/) which helps with generating conforming > x3d output. > > Best regards, Andreas > > On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir > <vla...@fm...> wrote: > > > > Dear Andreas, > > > > thank you very much for your help. Your solution is what I was searching for. > > Yes, it is a good idea to add the description to the log message. > > > > best regards, Vlado > > > > Vladimir Batagelj > > > > > > ________________________________ > > From: Andreas Plesch <and...@gm...> > > Sent: Sunday, January 15, 2023 5:51 AM > > To: Batagelj, Vladimir <vla...@fm...> > > Cc: x3d...@li... <x3d...@li...> > > Subject: Re: [x3dom-developers] Anchor description > > > > Hi Vladimir, > > > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > > has the standard specification of the Anchor node. It is mostly used > > with an URL to load other content. > > > > How the description field is used varies from browser to browser. > > x3dom shows a message in the debug log ("d" key) but it does not > > currently include the description. It is probably a good idea to add > > the description to the log message in an update. > > > > If you want to stay with an X3D only solution, you could use a > > TouchSensor and route the description field to a Text node, in some > > way. > > > > But it sounds like you are considering a javascript/HTML solution. You > > would need to know a little bit about HTML/DOM and javascript. > > > > Ok, I put together a codepen which shows one way to listen to a click > > event on an Anchor and then use the description on the web page: > > > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 > > > > It follows more or less the example you found but without jquery and a > > bit simpler. Take a look, > > > > Cheers, Andreas > > > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > > <vla...@fm...> wrote: > > > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > > > How can I achieve this in X3DOM ? > > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html says > > > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html, which is very close to the solution of my problem. I tried to adapt it without success. > > > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > > > best, > > > > > > Vladimir Batagelj > > > > > > > > > _______________________________________________ > > > x3dom-developers mailing list > > > x3d...@li... > > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers > > > > > > > > -- > > Andreas Plesch > > Waltham, MA 02453 > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Brutzman, D. (D. (CIV) <bru...@np...> - 2023-01-17 08:03:21
|
Vlado, your 3D data visualization example is super impressive. Wow! Thanks also for including link to paper on Emergence of Network Features from Multiplexity for European airports core of order 13. With your permission I'd like to share this work on Web3D twitter site. As you wish - please advise if that is OK. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br bru...@np... Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman From: Batagelj, Vladimir <vla...@fm...> Sent: Monday, January 16, 2023 6:00 PM To: Andreas Plesch <and...@gm...> Cc: x3d...@li... Subject: Re: [x3dom-developers] Anchor description Dear Andreas, thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom a page with the scene included from another file using <Inline> http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline and an example of its application in 3D data visualization http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . best regards, Vlado Vladimir Batagelj http://vladowiki.fmf.uni-lj.si/doku.php?id=vb _____ From: Andreas Plesch <and...@gm... <mailto:and...@gm...> > Sent: Monday, January 16, 2023 12:49 AM To: Batagelj, Vladimir <vla...@fm... <mailto:vla...@fm...> > Cc: x3d...@li... <mailto:x3d...@li...> <x3d...@li... <mailto:x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description Hi Vlado, Super. Please feel free to share any interesting results, perhaps of networks, on x3dom-developers, x3dom-users or the x3d-public mailing lists. I added the description field value to the log output in the latest dev version, and fixed Anchor behaviour for empty urls as it is explicitly specified. You may be interested in the x3d python package (https://pypi.org/project/x3d/ <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org% 2Fproject%2Fx3d%2F&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae0 8daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180% 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi LCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=ahTcucjog3xGO%2BK%2F93DiG4oARD0X2%2Fk3b ewC5TACy6Q%3D&reserved=0> ) which helps with generating conforming x3d output. Best regards, Andreas On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir <vla...@fm... <mailto:vla...@fm...> > wrote: > > Dear Andreas, > > thank you very much for your help. Your solution is what I was searching for. > Yes, it is a good idea to add the description to the log message. > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm... <mailto:and...@gm...> > > Sent: Sunday, January 15, 2023 5:51 AM > To: Batagelj, Vladimir <vla...@fm... <mailto:vla...@fm...> > > Cc: x3d...@li... <mailto:x3d...@li...> <x3d...@li... <mailto:x3d...@li...> > > Subject: Re: [x3dom-developers] Anchor description > > Hi Vladimir, > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > has the standard specification of the Anchor node. It is mostly used > with an URL to load other content. > > How the description field is used varies from browser to browser. > x3dom shows a message in the debug log ("d" key) but it does not > currently include the description. It is probably a good idea to add > the description to the log message in an update. > > If you want to stay with an X3D only solution, you could use a > TouchSensor and route the description field to a Text node, in some > way. > > But it sounds like you are considering a javascript/HTML solution. You > would need to know a little bit about HTML/DOM and javascript. > > Ok, I put together a codepen which shows one way to listen to a click > event on an Anchor and then use the description on the web page: > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodepen.i o%2Fandreasplesch%2Fpen%2FJjByYQa%3Feditors%3D1000&data=05%7C01%7Cbrutzman%4 0nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f757896337 8e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Vl6Mjnl vL6XRjWF5tPvl5a6nT1HiFfmITmdVot8KbNw%3D&reserved=0> > > It follows more or less the example you found but without jquery and a > bit simpler. Take a look, > > Cheers, Andreas > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > <vla...@fm... <mailto:vla...@fm...> > wrote: > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > How can I achieve this in X3DOM ? > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom .org%2Fauthor%2FNetworking%2FAnchor.html&data=05%7C01%7Cbrutzman%40nps.edu%7 Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0 %7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2 luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=0OSHhsPvxTTtb%2BD 86%2BZ7jvcAiFGRIoqvjmQRxM907Fw%3D&reserved=0> says > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom .org%2Ftutorials%2FanimationInteraction%2Fpicking%2Fexample.html&data=05%7C0 1%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea 9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIj oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C &sdata=VKiNHzqPKT%2BBLDwIwylD%2Fl5RuXoQa0tKQzuDsEM9EQo%3D&reserved=0> , which is very close to the solution of my problem. I tried to adapt it without success. > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > best, > > > > Vladimir Batagelj > > > > > > _______________________________________________ > > x3dom-developers mailing list > > x3d...@li... <mailto:x3d...@li...> > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sou rceforge.net%2Flists%2Flistinfo%2Fx3dom-developers&data=05%7C01%7Cbrutzman%4 0nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f757896337 8e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=%2BCobI h61bolXwOq9TyqMK0BQyYBx4fP3NXuCULqKhOk%3D&reserved=0> > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Brutzman, D. (D. (CIV) <bru...@np...> - 2023-01-17 04:50:34
|
Thanks for permission to share. Two tweets posted, with visualization screenshot and publication-figures image. * Interesting 3D scientific visualization of European airport data using #X3DOM for display of results within HTML page. Enables user-selected visual exploration of structural properties in European Air Transportation Multiplex Network. http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore * Visualization by Vladimir Batagelj, University of Ljubljana Slovenia, using dataset from "Emergence of network features from multiplexity" by Alessio Cardillo et al. in (Nature) Scientific Reports 3, 1344 (2013). http://complex.unizar.es/~atnmultiplex * Thread online at https://twitter.com/Web3DConsortium/status/1615182189645426688 Also thanks for sharing techniques on x3dom-developers list, wishing good progress with your continuing efforts. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br bru...@np... Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman From: Brutzman, Donald (Don) (CIV) <bru...@np...> Sent: Monday, January 16, 2023 6:29 PM To: Batagelj, Vladimir <vla...@fm...>; Andreas Plesch <and...@gm...> Cc: x3d...@li...; Brutzman, Donald (Don) (CIV) <bru...@np...> Subject: RE: [x3dom-developers] Anchor description; Vlado, your 3D data visualization example is super impressive. Wow! Thanks also for including link to paper on Emergence of Network Features from Multiplexity for European airports core of order 13. With your permission I'd like to share this work on Web3D twitter site. As you wish - please advise if that is OK. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br bru...@np... <mailto:bru...@np...> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman From: Batagelj, Vladimir <vla...@fm...> Sent: Monday, January 16, 2023 6:00 PM To: Andreas Plesch <and...@gm... <mailto:and...@gm...> > Cc: x3d...@li... <mailto:x3d...@li...> Subject: Re: [x3dom-developers] Anchor description Dear Andreas, thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom a page with the scene included from another file using <Inline> http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline and an example of its application in 3D data visualization http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . best regards, Vlado Vladimir Batagelj http://vladowiki.fmf.uni-lj.si/doku.php?id=vb _____ From: Andreas Plesch <and...@gm... <mailto:and...@gm...> > Sent: Monday, January 16, 2023 12:49 AM To: Batagelj, Vladimir <vla...@fm... <mailto:vla...@fm...> > Cc: x3d...@li... <mailto:x3d...@li...> <x3d...@li... <mailto:x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description Hi Vlado, Super. Please feel free to share any interesting results, perhaps of networks, on x3dom-developers, x3dom-users or the x3d-public mailing lists. I added the description field value to the log output in the latest dev version, and fixed Anchor behaviour for empty urls as it is explicitly specified. You may be interested in the x3d python package (https://pypi.org/project/x3d/ <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org% 2Fproject%2Fx3d%2F&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae0 8daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180% 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi LCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=ahTcucjog3xGO%2BK%2F93DiG4oARD0X2%2Fk3b ewC5TACy6Q%3D&reserved=0> ) which helps with generating conforming x3d output. Best regards, Andreas On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir <vla...@fm... <mailto:vla...@fm...> > wrote: > > Dear Andreas, > > thank you very much for your help. Your solution is what I was searching for. > Yes, it is a good idea to add the description to the log message. > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm... <mailto:and...@gm...> > > Sent: Sunday, January 15, 2023 5:51 AM > To: Batagelj, Vladimir <vla...@fm... <mailto:vla...@fm...> > > Cc: x3d...@li... <mailto:x3d...@li...> <x3d...@li... <mailto:x3d...@li...> > > Subject: Re: [x3dom-developers] Anchor description > > Hi Vladimir, > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > has the standard specification of the Anchor node. It is mostly used > with an URL to load other content. > > How the description field is used varies from browser to browser. > x3dom shows a message in the debug log ("d" key) but it does not > currently include the description. It is probably a good idea to add > the description to the log message in an update. > > If you want to stay with an X3D only solution, you could use a > TouchSensor and route the description field to a Text node, in some > way. > > But it sounds like you are considering a javascript/HTML solution. You > would need to know a little bit about HTML/DOM and javascript. > > Ok, I put together a codepen which shows one way to listen to a click > event on an Anchor and then use the description on the web page: > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodepen.i o%2Fandreasplesch%2Fpen%2FJjByYQa%3Feditors%3D1000&data=05%7C01%7Cbrutzman%4 0nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f757896337 8e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Vl6Mjnl vL6XRjWF5tPvl5a6nT1HiFfmITmdVot8KbNw%3D&reserved=0> > > It follows more or less the example you found but without jquery and a > bit simpler. Take a look, > > Cheers, Andreas > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > <vla...@fm... <mailto:vla...@fm...> > wrote: > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > How can I achieve this in X3DOM ? > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom .org%2Fauthor%2FNetworking%2FAnchor.html&data=05%7C01%7Cbrutzman%40nps.edu%7 Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0 %7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2 luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=0OSHhsPvxTTtb%2BD 86%2BZ7jvcAiFGRIoqvjmQRxM907Fw%3D&reserved=0> says > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom .org%2Ftutorials%2FanimationInteraction%2Fpicking%2Fexample.html&data=05%7C0 1%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea 9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIj oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C &sdata=VKiNHzqPKT%2BBLDwIwylD%2Fl5RuXoQa0tKQzuDsEM9EQo%3D&reserved=0> , which is very close to the solution of my problem. I tried to adapt it without success. > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > best, > > > > Vladimir Batagelj > > > > > > _______________________________________________ > > x3dom-developers mailing list > > x3d...@li... <mailto:x3d...@li...> > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sou rceforge.net%2Flists%2Flistinfo%2Fx3dom-developers&data=05%7C01%7Cbrutzman%4 0nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f757896337 8e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=%2BCobI h61bolXwOq9TyqMK0BQyYBx4fP3NXuCULqKhOk%3D&reserved=0> > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Batagelj, V. <vla...@fm...> - 2023-01-17 04:05:31
|
OK, Vlado Vladimir Batagelj<http://vladowiki.fmf.uni-lj.si/doku.php?id=vb> ________________________________ From: Brutzman, Donald (Don) (CIV) Sent: Tuesday, January 17, 2023 3:29 AM To: Batagelj, Vladimir; Andreas Plesch Cc: x3d...@li...; Brutzman, Donald (Don) (CIV) Subject: RE: [x3dom-developers] Anchor description; Vlado, your 3D data visualization example is super impressive. Wow! Thanks also for including link to paper on Emergence of Network Features from Multiplexity for European airports core of order 13. With your permission I’d like to share this work on Web3D twitter site. As you wish - please advise if that is OK. all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br bru...@np... Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman From: Batagelj, Vladimir <vla...@fm...> Sent: Monday, January 16, 2023 6:00 PM To: Andreas Plesch <and...@gm...> Cc: x3d...@li... Subject: Re: [x3dom-developers] Anchor description Dear Andreas, thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom a page with the scene included from another file using <Inline> http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline and an example of its application in 3D data visualization http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . best regards, Vlado Vladimir Batagelj http://vladowiki.fmf.uni-lj.si/doku.php?id=vb ________________________________ From: Andreas Plesch <and...@gm...<mailto:and...@gm...>> Sent: Monday, January 16, 2023 12:49 AM To: Batagelj, Vladimir <vla...@fm...<mailto:vla...@fm...>> Cc: x3d...@li...<mailto:x3d...@li...> <x3d...@li...<mailto:x3d...@li...>> Subject: Re: [x3dom-developers] Anchor description Hi Vlado, Super. Please feel free to share any interesting results, perhaps of networks, on x3dom-developers, x3dom-users or the x3d-public mailing lists. I added the description field value to the log output in the latest dev version, and fixed Anchor behaviour for empty urls as it is explicitly specified. You may be interested in the x3d python package (https://pypi.org/project/x3d/<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fx3d%2F&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=ahTcucjog3xGO%2BK%2F93DiG4oARD0X2%2Fk3bewC5TACy6Q%3D&reserved=0>) which helps with generating conforming x3d output. Best regards, Andreas On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir <vla...@fm...<mailto:vla...@fm...>> wrote: > > Dear Andreas, > > thank you very much for your help. Your solution is what I was searching for. > Yes, it is a good idea to add the description to the log message. > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm...<mailto:and...@gm...>> > Sent: Sunday, January 15, 2023 5:51 AM > To: Batagelj, Vladimir <vla...@fm...<mailto:vla...@fm...>> > Cc: x3d...@li...<mailto:x3d...@li...> <x3d...@li...<mailto:x3d...@li...>> > Subject: Re: [x3dom-developers] Anchor description > > Hi Vladimir, > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > has the standard specification of the Anchor node. It is mostly used > with an URL to load other content. > > How the description field is used varies from browser to browser. > x3dom shows a message in the debug log ("d" key) but it does not > currently include the description. It is probably a good idea to add > the description to the log message in an update. > > If you want to stay with an X3D only solution, you could use a > TouchSensor and route the description field to a Text node, in some > way. > > But it sounds like you are considering a javascript/HTML solution. You > would need to know a little bit about HTML/DOM and javascript. > > Ok, I put together a codepen which shows one way to listen to a click > event on an Anchor and then use the description on the web page: > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodepen.io%2Fandreasplesch%2Fpen%2FJjByYQa%3Feditors%3D1000&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Vl6MjnlvL6XRjWF5tPvl5a6nT1HiFfmITmdVot8KbNw%3D&reserved=0> > > It follows more or less the example you found but without jquery and a > bit simpler. Take a look, > > Cheers, Andreas > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > <vla...@fm...<mailto:vla...@fm...>> wrote: > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > How can I achieve this in X3DOM ? > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom.org%2Fauthor%2FNetworking%2FAnchor.html&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=0OSHhsPvxTTtb%2BD86%2BZ7jvcAiFGRIoqvjmQRxM907Fw%3D&reserved=0> says > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom.org%2Ftutorials%2FanimationInteraction%2Fpicking%2Fexample.html&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=VKiNHzqPKT%2BBLDwIwylD%2Fl5RuXoQa0tKQzuDsEM9EQo%3D&reserved=0>, which is very close to the solution of my problem. I tried to adapt it without success. > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > best, > > > > Vladimir Batagelj > > > > > > _______________________________________________ > > x3dom-developers mailing list > > x3d...@li...<mailto:x3d...@li...> > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fx3dom-developers&data=05%7C01%7Cbrutzman%40nps.edu%7Cf8b8f6fd53a847f903ae08daf830b4f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638095185463995180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=%2BCobIh61bolXwOq9TyqMK0BQyYBx4fP3NXuCULqKhOk%3D&reserved=0> > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Batagelj, V. <vla...@fm...> - 2023-01-17 02:15:28
|
Dear Andreas, thank you very much for your help. To document the solutions, I prepared three wiki pages: a page with a single-file solution http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3dom a page with the scene included from another file using <Inline> http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:inline and an example of its application in 3D data visualization http://vladowiki.fmf.uni-lj.si/doku.php?id=vlado:work:2m:mwn:x3d:aircore It still remains the question of why it (Anchor description) doesn't work when browsing a local HTML file or an HTML file from a server http://vlado.fmf.uni-lj.si/test/anchor.htm . best regards, Vlado Vladimir Batagelj<http://vladowiki.fmf.uni-lj.si/doku.php?id=vb> ________________________________ From: Andreas Plesch <and...@gm...> Sent: Monday, January 16, 2023 12:49 AM To: Batagelj, Vladimir <vla...@fm...> Cc: x3d...@li... <x3d...@li...> Subject: Re: [x3dom-developers] Anchor description Hi Vlado, Super. Please feel free to share any interesting results, perhaps of networks, on x3dom-developers, x3dom-users or the x3d-public mailing lists. I added the description field value to the log output in the latest dev version, and fixed Anchor behaviour for empty urls as it is explicitly specified. You may be interested in the x3d python package (https://pypi.org/project/x3d/) which helps with generating conforming x3d output. Best regards, Andreas On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir <vla...@fm...> wrote: > > Dear Andreas, > > thank you very much for your help. Your solution is what I was searching for. > Yes, it is a good idea to add the description to the log message. > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm...> > Sent: Sunday, January 15, 2023 5:51 AM > To: Batagelj, Vladimir <vla...@fm...> > Cc: x3d...@li... <x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description > > Hi Vladimir, > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > has the standard specification of the Anchor node. It is mostly used > with an URL to load other content. > > How the description field is used varies from browser to browser. > x3dom shows a message in the debug log ("d" key) but it does not > currently include the description. It is probably a good idea to add > the description to the log message in an update. > > If you want to stay with an X3D only solution, you could use a > TouchSensor and route the description field to a Text node, in some > way. > > But it sounds like you are considering a javascript/HTML solution. You > would need to know a little bit about HTML/DOM and javascript. > > Ok, I put together a codepen which shows one way to listen to a click > event on an Anchor and then use the description on the web page: > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 > > It follows more or less the example you found but without jquery and a > bit simpler. Take a look, > > Cheers, Andreas > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > <vla...@fm...> wrote: > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > How can I achieve this in X3DOM ? > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html says > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html, which is very close to the solution of my problem. I tried to adapt it without success. > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > best, > > > > Vladimir Batagelj > > > > > > _______________________________________________ > > x3dom-developers mailing list > > x3d...@li... > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Andreas P. <and...@gm...> - 2023-01-15 23:48:25
|
Hi Vlado, Super. Please feel free to share any interesting results, perhaps of networks, on x3dom-developers, x3dom-users or the x3d-public mailing lists. I added the description field value to the log output in the latest dev version, and fixed Anchor behaviour for empty urls as it is explicitly specified. You may be interested in the x3d python package (https://pypi.org/project/x3d/) which helps with generating conforming x3d output. Best regards, Andreas On Sun, Jan 15, 2023 at 6:04 PM Batagelj, Vladimir <vla...@fm...> wrote: > > Dear Andreas, > > thank you very much for your help. Your solution is what I was searching for. > Yes, it is a good idea to add the description to the log message. > > best regards, Vlado > > Vladimir Batagelj > > > ________________________________ > From: Andreas Plesch <and...@gm...> > Sent: Sunday, January 15, 2023 5:51 AM > To: Batagelj, Vladimir <vla...@fm...> > Cc: x3d...@li... <x3d...@li...> > Subject: Re: [x3dom-developers] Anchor description > > Hi Vladimir, > > https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html > has the standard specification of the Anchor node. It is mostly used > with an URL to load other content. > > How the description field is used varies from browser to browser. > x3dom shows a message in the debug log ("d" key) but it does not > currently include the description. It is probably a good idea to add > the description to the log message in an update. > > If you want to stay with an X3D only solution, you could use a > TouchSensor and route the description field to a Text node, in some > way. > > But it sounds like you are considering a javascript/HTML solution. You > would need to know a little bit about HTML/DOM and javascript. > > Ok, I put together a codepen which shows one way to listen to a click > event on an Anchor and then use the description on the web page: > > https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 > > It follows more or less the example you found but without jquery and a > bit simpler. Take a look, > > Cheers, Andreas > > On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir > <vla...@fm...> wrote: > > > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > > > How can I achieve this in X3DOM ? > > The documentation https://doc.x3dom.org/author/Networking/Anchor.html says > > > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html, which is very close to the solution of my problem. I tried to adapt it without success. > > > > Can somebody help me to adapt this example or suggest some other approach? > > > > best, > > > > Vladimir Batagelj > > > > > > _______________________________________________ > > x3dom-developers mailing list > > x3d...@li... > > https://lists.sourceforge.net/lists/listinfo/x3dom-developers > > > > -- > Andreas Plesch > Waltham, MA 02453 -- Andreas Plesch Waltham, MA 02453 |
From: Batagelj, V. <vla...@fm...> - 2023-01-15 23:20:12
|
Dear Andreas, thank you very much for your help. Your solution is what I was searching for. Yes, it is a good idea to add the description to the log message. best regards, Vlado Vladimir Batagelj<http://vladowiki.fmf.uni-lj.si/doku.php?id=vb> ________________________________ From: Andreas Plesch <and...@gm...> Sent: Sunday, January 15, 2023 5:51 AM To: Batagelj, Vladimir <vla...@fm...> Cc: x3d...@li... <x3d...@li...> Subject: Re: [x3dom-developers] Anchor description Hi Vladimir, https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html has the standard specification of the Anchor node. It is mostly used with an URL to load other content. How the description field is used varies from browser to browser. x3dom shows a message in the debug log ("d" key) but it does not currently include the description. It is probably a good idea to add the description to the log message in an update. If you want to stay with an X3D only solution, you could use a TouchSensor and route the description field to a Text node, in some way. But it sounds like you are considering a javascript/HTML solution. You would need to know a little bit about HTML/DOM and javascript. Ok, I put together a codepen which shows one way to listen to a click event on an Anchor and then use the description on the web page: https://codepen.io/andreasplesch/pen/JjByYQa?editors=1000 It follows more or less the example you found but without jquery and a bit simpler. Take a look, Cheers, Andreas On Fri, Jan 13, 2023 at 8:55 PM Batagelj, Vladimir <vla...@fm...> wrote: > > In my X3D files, I am using node <Anchor> with the attribute description. See the attached X3D file. This enables me in some X3D viewers to identify a node by pointing to it. In the viewer view3dscene (see the attached PNG) I pointed to the red node and obtained in the report window the corresponding description info "1: Fire". > > How can I achieve this in X3DOM ? > The documentation https://doc.x3dom.org/author/Networking/Anchor.html says > > The description field in the Anchor node specifies a textual description of the Anchor node. This may be used by browser-specific user interfaces that wish to present users with more detailed information about the Anchor. > > I found an example, see https://doc.x3dom.org/tutorials/animationInteraction/picking/example.html, which is very close to the solution of my problem. I tried to adapt it without success. > > Can somebody help me to adapt this example or suggest some other approach? > > best, > > Vladimir Batagelj > > > _______________________________________________ > x3dom-developers mailing list > x3d...@li... > https://lists.sourceforge.net/lists/listinfo/x3dom-developers -- Andreas Plesch Waltham, MA 02453 |