On Sat, Jul 21, 2007 at 10:41:27PM -1000, Eric Firing wrote: > You raised the question of 3D. I don't know anything about fancy 3D > with hardware acceleration etc., but for the simplest 3D it seems like > everything can be done at the model stage of the transformation; > everything after that is 2D. Maybe this doesn't get us very far; I > don't know how hidden-line removal would be handled for multiple paths.
I tried to work on gnuplot a while ago, adding some 3D features. My contribution ended up being inexistant (a physics undergrad with no experience in C doesn't get terribly far on this kind of project), but I did learn something: a 3D package must be fully 3D, or I think it won't go far. My personnal opinion is that I won't spend my time on a package that wants to do 3D and that does not keep a complete 3D representation of its object at all time, and even feeds it to the backends. <shameless plug> If you want cool 3D, come and help us with mayavi 2D, we are currently working on a pylab like interface. It is in its early stages, but if more people work on it, it will go far </shameless plug>. If you are going down the 3D slope you should define precisely what you want to do, and where you stop, and think the architecture in these terms. The big question is: when does the projection happen ? What lives in the 2D canvas (IMHO, the less, the better), what live in the 3D world, and when is it projected. My 2 cents, Gaël ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
