|
From: Phil F. <pfe...@co...> - 2002-12-30 19:38:58
|
Tom, I've been looking through my DisplaySurface3D code and I'm thinking that the canvas3D/SimpleUniverse split will make things uglier. The reason is that PickUtilities requires both the canvas3D and the root of the scene graph in which the picking will take place. That means that the display and surface classes would have to have enough knowledge of each other that splitting them doesn't' make sense to me. Additionally, SimpleUniverse actually supports only *one* Canvase3D, even thought there is a getCanvas that can retrieve by index. Rather than that, what might work easier is to have the particular scene graph generated or imported by the user load into a UserSceneGraph class that would correspond (somewhat) to Display. You could have classes for CustomSceneGraph, XMLSceneGraph, etc that would handle the particulars of the scene graph setup and feed them to the DisplaySurface3D. Thoughts? Phil |