[x3d-public] X3D-Edit 4.0 release: HTML5 id/class/style, links for Ultimaker Cura (3D printing)

Sun Jun 20 20:42:07 PDT 2021

The CORS work remains under testing and development.

Node.js http server is possible but not a common install for end users, and so integrating a native Java and Jetty approaches are preferred for authors testing a model conversion.  We've added Python as an option to X3D-Edit since that is fairly common and easy to test.

Thanks but no thanks for server keys, we won't be distributing anything like that with X3D-Edit.  Design goal remains safe and secure throughout.

No need for https since this is for local user on local machine testing that their X3D model can run together with X_ITE or X3DOM.

As you can see from below, link obfuscation at NPS (provided by Microsoft) is pretty severe.

Take care.

On 6/20/2021 8:12 PM, John Carlson wrote:
> 
> 
> Python didn't pan out, so I switch back to Node.JS and a modicum of success.
> 
> Here are the diffs so far:
> 
> NodeJSHttpsSerer$ diff
> /c/x3d-code/www.web3d.org/x3d/content/examples/HelloWorldX3dom.xhtml
> HelloWorldX3dom.xhtml
> 17c17
> < href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom.org%2Fdownload%2Fdev%2Fx3dom.css%2522%2F&data=04%7C01%7Cbrutzman%40nps.edu%7Ceb5e733342c84e1e1bf008d9346273df%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637598419722512831%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Vqm4BZZzuCTGh2%2B%2BJhnqdpF73rmiPWw8i5VT6yszfFs%3D&reserved=0>
> ---
>  > href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.x3dom.org%2Fdownload%2Fdev%2Fx3dom.css%2522%2F&data=04%7C01%7Cbrutzman%40nps.edu%7Ceb5e733342c84e1e1bf008d9346273df%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637598419722512831%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DpC7xi4l5kRaUaQk%2FuvYueGe12yTSVDefaM9O7w5MMw%3D&reserved=0>
> 19c19
> < src="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.x3dom.org%2Fdownload%2Fdev%2Fx3dom-full.js%2522%2F&data=04%7C01%7Cbrutzman%40nps.edu%7Ceb5e733342c84e1e1bf008d9346273df%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637598419722512831%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ny0nCtlx7nc3boEasS7bV%2FYInr%2Fte%2FPaTvNJIiEnJYU%3D&reserved=0>
> ---
>  > src="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.x3dom.org%2Fdownload%2Fdev%2Fx3dom-full.js%2522%2F&data=04%7C01%7Cbrutzman%40nps.edu%7Ceb5e733342c84e1e1bf008d9346273df%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637598419722512831%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5qsZKwka0ganDZZVaZ3vRg9A%2BFG9cZMLSMp2rV8vS9A%3D&reserved=0>
> 183c183
> <    <body id="htmlBody" onload="toggleFullscreen ();">
> ---
>  >    <body id="htmlBody" onload="/*toggleFullscreen ();*/">
> 
> 
> (replace doc with www in downloads, comment out toggleFullscreen, since
> it doesn't seem to be defined.
> 
> 
> I might try to figure out how to set up fonts for X3DOM, it's been a
> long time since I looked at them.
> 
> 
> Node.JS server seems to be working with HTTPS, I'll work on creating a
> zip/repository for interested people.
> 
> John
> 
> 
> 
> On 6/20/21 9:18 PM, John Carlson wrote:
>> I didn't have much luck setting up Node.JS for this.  I will try to
>> use my keys with python3 next.
>>
>> John
>>
>> On 6/20/21 8:40 PM, John Carlson wrote:
>>> Your CORS example uses http, not https, as talked about in the CORS
>>> text.  The X3DOM example does not work.  X_ITE example is good.
>>>
>>> I can help you set up a Node.JS HTTPS server (you can't use X3DJSONLD
>>> becase I haven't checked in the keys, but I probably should, because
>>> it's localhost).
>>>
>>> It should be easy enough to set up a pair of keys to use on
>>> localhost, and check the keys into a repository.  (yes, localhost
>>> will work with the same encryption keys on any machine.  At least
>>> they did last time I encountered this issue).
>>>
>>> Don, I trust you with my server keys, so I will send them to you when
>>> you're back.  Then we can use the X3DJSONLD's app.js (minus
>>> enhancements).
>>>
>>> Others may have other suggestions for HTTPS, but at a minimum, you
>>> need keys targeted at your server name (localhost or other). Also,
>>> I'm unsure if Node.js does the WebDAV thing, so you may have to
>>> specify the models directly.
>>>
>>> I will set up a minimal project right now, then check out X3d-Edit.
>>>
>>> You said you wouldn't run Node.js?  How is it worse than python3?
>>>
>>> John
>>>
>>> On 6/20/21 1:28 PM, Don Brutzman wrote:
>>>> X3D-Edit 4.0 beta has another release: includes refactored DEF/USE
>>>> panel with tabbed support for HTML5 id/class/style, added links for
>>>> Ultimaker Cura (3D printing).
>>>>
>>>> * https://savage.nps.edu/X3D-Edit/#Downloads
>>>>
>>>> Also includes partial CORS support, testing and integration continues.
>>>>
>>>> * X3D Scene Authoring Hints: Cross-Origin Resource Sharing (CORS)
>>>> https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#CORS
>>>>
>>>>
>>>> All reports welcome (Windows Mac Linux).  Have fun with X3D-Edit! 8)

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman