Re: [matplotlib-devel] Updating MPlot3D to a more recent matplotlib.

[Ondrej C. <on...@ce...>]

On Sun, Mar 8, 2009 at 7:45 PM, Jonathan Taylor
<jon...@ut...> wrote:
> Hi Reinier,
>
> Awesome.  Those plots are making me smile! I also agree with your
> refactoring and have applied your patch to my git repository.
>
> I agree with you concerning the sympy plotting routines.  I think what
> we have here is quite flexible and does a very good job of replicating
> the equivalent functionality of MATLAB.  I think it would be a huge
> effort trying to make 2D plots and 3D plots look consistent if another
> approach was taken.  Indeed, this is a desirable characteristic.  In
> addition, the code is actually very short and easy to maintain.  Given
> that matplotlib has had trouble maintaining 3D code in the past, it
> might not be a good idea to switch to a more complicated codebase.
>
> You should grab some of my more recent changes as I have added a few
> more fixes.  Most importantly, if you reuse the same figure, the old
> event handlers will still attached preventing Axes objects from dieing
> and causing interactive manipulation of the plots to be very sluggish.
>  Also, in terms of performance, I have found that switching to TkAgg
> from GTKAgg was helpful.
>
> Also, I think the original code from John Porter was under a BSD
> license.  I am thinking of adding our names and the BSD license to the
> top of each file to protect it while its not officially part of
> matplotlib.  What do you think?

A trivial patch is attached to make proj3d.py work.

I tried the examples and it looks great. However, it's pretty slow, at
least on my machine. The plotting in sympy is much faster. Is there
some way to make the mplot3d faster?

Ondrej