On Jan 13, 2008 10:10 AM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > Fernando Perez wrote: > > On Jan 12, 2008 12:48 PM, Jaap Spies <[EMAIL PROTECTED]> wrote: > >> Fabio Tonti wrote: > >>> Looks good, but seriosly: why don't we stick to the Mayavi/TVTK stuff from > >>> Enthought??? > >>> > >> You should try! See the actual movies. Haven't seen that in mayavi. > >> Try the examples and see how easy it is to visualize movement and other > >> physics. Try for example the kinetics kit. > > > > There's an experimental implementation of vpython for tvtk, done by a > > student of Prabhu. Currently the Traits overhead makes it > > significantly slower than vpython, but it was just a quick hack, so it > > may be possible to get all the vpython speed back. The api is > > identical. > > > > Not so identical! I've been playing with enthought.tvtk.tools.visual. > Most(?) or some of VPython is there, but I'm missing the scene class. > In VPython you can interact with the scene on screen with mouse > events. This is an important feature! For example you can move individual > objects around, etcetera.
I should have said 'fairly similar' rather than 'identical', since I was going on memory. Sorry about that. > This module is clearly not finished. From visual.py: Certainly. That I remembered, and I said as much. That's what the words 'experimental' and 'quick hack' that I used typically imply, but I'll do my best to be clearer next time. It would be great to have this work well, which is why I mentioned it, to see if a volunteer might pick it up. I'm a big fan of vpython, but since I already use VTK for 'real work', I'd much rather have a vtk-based system with similar capabilities than having to deal with yet-another-opengl-mainloop. Part of the problem with vpython is that I don't know how to run vpython scripts as part of a persistent interactive session, since it initializes the OpenGL event loop at startup always. So you basically can only run them as standalone scripts, starting a fresh python process each time. This is OK for little toy stuff, but annoying for heavy-duty work with large codes where initialization and module loading can take a long time. TVTK doesn't have that issue. Anyway, I just mentioned this in case you (or anyone else) was interested in picking this up. The more capabilities we get from a few *well integrated* tools, the more we all win. But I don't have the bandwidth to do any work on this myself (what TVTK/mayavi2 can do is already perfect for my work needs, and for me the vpython-like funcitonality is currently just 'for fun'), so there's not much point in me continuing here. If this interests you, as Prabhu said he'd welcome patches to finish it up. Else feel free to use vpython which already exists and is very nice (even if you can't easily benefit from the rest of tvtk with it), or whatever else suits your needs. Cheers, f --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
