Do we wanna update to d3.v...4?5?

[Fumeng-Yang]

I tried both today. I think we can update to v4 with some minor changes.
However, in d3.v5, "HTML parsing requires a global document and relies on DOM Ranges, which are not supported by JSDOM as of version 8.3, thus, this method is supported in browsers but not in Node". We need to find another way to load HTML pages.

[codementum]

Couldn't we still do v5, however, since the main d3.html call comes from the client?

[Fumeng-Yang]

👋hmmm... I didn't get it. Could you be more specific?

[codementum]

"HTML parsing requires a global document and relies on DOM Ranges, which are not supported by JSDOM as of version 8.3, thus, this method is supported in browsers but not in Node".

^ It looks like you can still do HTML parsing in the browser, which is where we call it, but not in node.
We don't use d3.html in node so we should be fine.
(Unless I'm missing something...)

[Fumeng-Yang]

I tried this morning.

-> d3.html() I don't think you used (=the initial version) it in node.js. Unless I miss something, isn't experimentr.js a native js file...
-> Calling d3.html() in the browser still doesn't work. Nothing happened. I don't know what I missed.
-> We can still do native js code, which does less for us, or JQuery. However, I'm scared of including too many libraries and messing up the current neat structure.

[Fumeng-Yang]

Ignore the first point above. Stupid Fumeng before the morning coffee. Anyway, I hope we can keep the current architecture. It is neat and flexible.

[codementum]

Ah, well if you've tried it and it doesn't work with v5, then maybe one of us will have to sit down one day and debug until we figure out which part is going wrong.

I agree 100% that avoiding other libraries (jquery) is desirable.

[Fumeng-Yang]

Ha. On my todos list, I will find a day to spend a few more hours on it. If I can't figure it out, I will leave it to you.
P.S. d3 v4 works properly and I am using the highest version of d3 v4 now. The only change to the original version is to rename a function call.

[Fumeng-Yang]

I did some work for v5 today. I think I can parse the html page and append them to the current page now. However, I don't think why <script> nodes don't execute when calling appendChild().

What's the best way for you so that I can get your input?

Two changes need to be made to experimentr.js:

• rename d3.xhr() to d3.request(); about L 81 inside experimentr.save()
• resolve d3.html(); about L 120 inside experimentr.activate()
  My progress (this can load html documents but the scripts nodes didn't execute.
  d3.html(sequence[x])
  .then(r => {d3.select('#module').node().appendChild(r.body)});

[codementum]

Oh interesting. Maybe we should make a branch and work on this feature, then merge back in once we get it working correctly.

[Fumeng-Yang]

yes, sir..

[Fumeng-Yang]

the versions for d3 v4 & v5 are up