Closed patrick-g-h closed 4 years ago
Hey Tristan - while currently it "stands alone," it should still (probably...) need to talk to the Python backend, and thus the Python parts need to be served by Flask, not just the JS frontend that gets exported. It currently works by "cheating" and just giving the frontend some data values in memory.
Anything to be done in the future with the 3d graph will likely not be amenable to the "export an html" workflow, so moving it into controller.py ensures all the pieces can talk to each other conveniently.
Cheers!
Okay, in that case this all looks good to me!
I have a branch where I made the changes I requested - let me know if you agree (@Park-Patrick) and I can just merge them into this branch.