From: Rob S. <sa...@ph...> - 2008-03-24 16:21:56
|
Yes, this would be a great idea. In some of my past programs, I've done that clumsy workaround ("a separate scene for each view, and copy each object into all of them,...") that you have suggested. In fact, my workaround raised the bug(?)/feature of copyobjects() in an earlier version of VPython. Here are some ideas where multiple-views of the same scene would be useful: - a zoomed-in view akin to a magnifying glass over the scene - top-view vs. side-views (as seen in engineering graphics) - different reference frames for two-body collisions, for inertial-vs-noninertial viewpoints, and for other relativistic situations [these are merely "camera" transformations] - alternate representations: spatial-vs-spacetime viewpoints [the spatial one being a "projection" of the spacetime one] It seems this multiple-viewpoint feature would require fewer Python objects and less bookkeeping of these objects... as well as be more faithfully representative of the idea that one physical situation is being viewed from different perspectives. rob salgado |
From: Jon S. <js...@gm...> - 2008-03-24 16:32:40
|
Another application is for immersive computing. We have created an inexpensive immersive four screen projection system. I should think that the stereoscopic capabilities in Vpython are already a start on this? On 3/24/08 12:21 PM, "Rob Salgado" <sa...@ph...> wrote: > > Yes, this would be a great idea. > > In some of my past programs, I've done that clumsy workaround > ("a separate scene for each view, and copy each object into all of them,...") > that you have suggested. In fact, my workaround raised the bug(?)/feature > of copyobjects() in an earlier version of VPython. > > Here are some ideas where multiple-views of the same scene would be useful: > > - a zoomed-in view akin to a magnifying glass over the scene > > - top-view vs. side-views (as seen in engineering graphics) > > - different reference frames for two-body collisions, for > inertial-vs-noninertial viewpoints, and for other relativistic situations > [these are merely "camera" transformations] > > - alternate representations: spatial-vs-spacetime viewpoints [the spatial > one being a "projection" of the spacetime one] > > It seems this multiple-viewpoint feature would require fewer Python > objects and less bookkeeping of these objects... as well as be more > faithfully representative of the idea that one physical situation is being > viewed from different perspectives. > > > rob salgado > > > > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users Jon Schull sc...@di... cell: 585-738-6696 Associate Professor Rochester Institute of Technology |
From: Bruce S. <Bru...@nc...> - 2008-03-24 17:18:51
|
At the technical architectural level of VPython, the stereo capability isn't really a start on having separate views. Rendering is done on a per-window (per-display) basis, with the added feature that if a display has stereo active, additional graphics are added to the display inside that rendering. It will probably require fairly major restructuring of Visual to achieve the desired effects of enabling multiple views on objects. We'll try to keep these interesting suggestions in mind in the intense work going on right now on improving Visual 4, but my guess is that multiple views won't happen soon. Bruce Sherwood Jon Schull wrote: > Another application is for immersive computing. We have created an > inexpensive immersive four screen projection system. > > I should think that the stereoscopic capabilities in Vpython are already a > start on this? > > > On 3/24/08 12:21 PM, "Rob Salgado" <sa...@ph...> wrote: > > >>Yes, this would be a great idea. >> >>In some of my past programs, I've done that clumsy workaround >>("a separate scene for each view, and copy each object into all of them,...") >>that you have suggested. In fact, my workaround raised the bug(?)/feature >>of copyobjects() in an earlier version of VPython. >> >>Here are some ideas where multiple-views of the same scene would be useful: >> >>- a zoomed-in view akin to a magnifying glass over the scene >> >>- top-view vs. side-views (as seen in engineering graphics) >> >>- different reference frames for two-body collisions, for >>inertial-vs-noninertial viewpoints, and for other relativistic situations >>[these are merely "camera" transformations] >> >>- alternate representations: spatial-vs-spacetime viewpoints [the spatial >>one being a "projection" of the spacetime one] >> >>It seems this multiple-viewpoint feature would require fewer Python >>objects and less bookkeeping of these objects... as well as be more >>faithfully representative of the idea that one physical situation is being >>viewed from different perspectives. >> >> >>rob salgado >> >> >> >> >> >> >> >> >> >>------------------------------------------------------------------------- >>This SF.net email is sponsored by: Microsoft >>Defy all challenges. Microsoft(R) Visual Studio 2008. >>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>_______________________________________________ >>Visualpython-users mailing list >>Vis...@li... >>https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > Jon Schull sc...@di... cell: 585-738-6696 > Associate Professor Rochester Institute of Technology > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |