> I am strongly in favor of keeping the entire commit history of
> trunk/matplotlib. While the repo is large now, most of the size comes
> from data and regression test images, and the early history is largely
> code so will not add much incremental size. I suppose one of the
> downsides of git i
Hi,
I cannot answer your questions specifically but perhaps I can provide some
insight. My current understanding is that most of mplot3d is a bit of a
hack. I say this because I use it daily and I was the one who hacked it
into a half working state out of necessity after it was originally fell o
Ben.
Sorry I did not see the other posts surrounding mplot3d or your patch. I am
very excited to have that though. Thank you.
My opinion about a redesign still stands though.
Jon.
On Thu, Feb 25, 2010 at 11:16 PM, Jonathan Taylor wrote:
> Hi,
>
> I cannot answer your questions spe
Hi John,
You should be able to check out a copy from my git repo via
git clone http://jonathantaylor.ca/mplot3d.git
cd mplot3d
git pull
I am missing Reiniers final update though but you should be able to
run demo.py and the first few examples in the __name__ == '__main__'
clause of axes3d.py.
B
ense it definitely
> sounds like a good idea to add it if it applies to the original code.
> Shall we try to work to some sort of easily-installable form of the
> again-working code?
>
> Regards,
> Reinier
>
> On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
> wrote:
>>
ere is the email that I sent to Jonathan only by a mistake:
>
> On Sun, Mar 8, 2009 at 9:44 PM, Jonathan Taylor
> wrote:
>> Just because we are using all the 2D drawing code to make the plots,
>> which is why the 3d code is so small, maintainable and is visually
>> consis
:
> On Sun, Mar 8, 2009 at 9:01 PM, Jonathan Taylor
> wrote:
>> Hi,
>>
>> Thanks for the patch. How slow is it for you? I find it slow but
>
> Well, when I use mouse to rotate the image, I can see that it lags behind.
>
>> quite usable. The main problem, I im
f I can somewhat speed some of it up by adding an
optional module to perform a few of these operations in C.
Jon.
On Sun, Mar 8, 2009 at 11:37 PM, Ondrej Certik wrote:
> On Sun, Mar 8, 2009 at 7:45 PM, Jonathan Taylor
> wrote:
>> Hi Reinier,
>>
>> Awesome. Those plots
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
Great. I applied your patch and pushed it to the web repository.
I agree, that some more serious refactoring might be good. I have
been leaving comments throughout the code with my thoughts on this.
Cheers,
Jon.
On Wed, Mar 4, 2009 at 4:53 AM, Reinier Heeres wrote:
> Hi all,
>
> I was also a
unter wrote:
>
>
> On Mon, Mar 2, 2009 at 10:13 PM, Jonathan Taylor
> wrote:
>>
>> Hi,
>>
>> I saw that 3D plotting was dropped from matplotlib since the last time
>> I used it. Unfortunately, it is pretty necessary for some of the work
>> I am doing.
Hi,
I saw that 3D plotting was dropped from matplotlib since the last time
I used it. Unfortunately, it is pretty necessary for some of the work
I am doing. Thus, I have started the process of refactoring the code
to work with recent versions of matplotlib.
Right now, it is still in very early
12 matches
Mail list logo
