Context Navigation

Changes between Version 1 and Version 2 of Ticket #12402, comment 66

v1	v2
9	9	2) The Three.js `Geometry` that I used for convenience needs to be replaced with `BufferGeometry`. This will improve use of available memory and avoid possible browser issues, as well as prepare for stability in notebooks. This is straightforward.
10	10
11		3) The code used for `line` objects needs to be completely rewritten. The is a hardware driver limitation on Windows machines that prevents rendering of line thickness in WebGL that is not going away soon, and I'm still thinking about the best way around this. Andrey certainly won't approve this ticket without line thickness rendering decently across hardware platforms, and I agree with him on that.
	11	3) The code used for `line` objects needs to be completely rewritten. There is a hardware driver limitation on Windows machines that prevents rendering of line thickness in WebGL that is not going away soon, and I'm still thinking about the best way around this. Andrey certainly won't approve this ticket without line thickness rendering decently across hardware platforms, and I agree with him on that.
12	12
13	13	4) Notebook integration needs to be added and tested. Since I am not familiar with the details of notebooks, this may not be straightforward without input from those more familiar. Adding a few Three.js files to a notebook page should be easy, but more than that may require modifying how the notebook dynamically handles `iframe` content. That might also be better dealt with on a separate ticket.