On 9/24/07, Eric Firing <[EMAIL PROTECTED]> wrote:
>
> John et al.,
>
> "Agg 2.5 will ship with a libsigc++ license that will allow us to treat
> the code as MIT X11 unless the code is pulled out, allowing Antigrain to
> be used internally for Silverlight and allowing them to license
> Antigrain fo
Curious, I gave it a try in photoshop. I think you have to line up the
doorways & windows to see the effect.
I see someone who looks kinda like they're holding a baby, but I don't know
what a Templar knight is supposed to look like, so I'm not sure if I saw
that or not.
--bb
On 7/29/07, Darren D
On 7/25/07, Chris Barker <[EMAIL PROTECTED]> wrote:
> Peter Wang wrote:
> > We've also had this discussion internally a bit. It usually
> > concludes with us wishing that someone would just port jsmath to
> > Python, or implement Knuth's TeX layout rules in Python. :)
>
> It looks like jsmath uses
On 7/25/07, Gael Varoquaux <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 24, 2007 at 05:31:17PM -0700, Chris Barker wrote:
> > > output when usetex is enabled.
>
> > Ah! and some good math implementation -- What does Chaco do for that? I
> > know I took part in a discussion about it on a Chaco list a
On 7/20/07, John Hunter <[EMAIL PROTECTED]> wrote:
> = Chaco and Kiva =
>
> It is a good idea for an enterprising developer to take a careful look
> at the current Chaco and Kiva to see if we can further integrate with
> them. I am gun shy because they seem formiddable and complex, and one
> of m
"Cheat commandos, Rock rock on."
Sounds great. This is sorely needed in matplotlib I think. But I have no
idea how to make it work. Mayavi is way to huge for the kind of simple 3D
plotting needs most folks have.
--bb
On 7/7/07, Nicolas Rougier <[EMAIL PROTECTED]> wrote:
Hi all,
I've been
On 7/7/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
Sorry to spam this list with this, but it came up here...
Carl Worth wrote:
>> http://www.scipy.org/License_Compatibility
>
> Thanks, John, for sharing this essay. Please allow me to respond to a
> few points:
I can't answer your quest
I'd personally be happy to move on to wxPython 2.8 but I'm using
enthought's matplotlib egg, which apparently requires enthought's
wxPython egg, and that's still at version 2.6.
--bb
On 4/12/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> The world of wxAgg and versions of wxPytho
On 4/5/07, Eric Firing <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
> [...]
> > As for your specific points:
> >
> > * inside matplotlib we should just use numpy everywhere. We need to
> > agree on some import convention. I'm happy with 'import numpy as nx'
> > though this might be confusing
McIvor <[EMAIL PROTECTED]> wrote:
On Sep 10, 2006, at 9:50 AM, Bill Baxter wrote:>> I've just uploaded two patch files that apply the changes discussed> in this thread.Thanks Bill. I'm sorry I've been dragging a** on getting your
patches reviewed. I'l
06
These were made against the latest release (xx.5 was it?)
Hopefully these will make it easer to integrate the changes.
--BillOn 7/31/06, Ken McIvor <[EMAIL PROTECTED]> wrote:> On Jul 30, 2006, at 8:07 AM, Bill Baxter wrote:> > I went ahead and implemented this yesterda
On 8/28/06, Darren Dale <[EMAIL PROTECTED]> wrote:
> A while back, I put some effort into rendering an offset ticklabel, which
> allowed the user to do something like
>
> plot(linspace(10100, 10200, 100))
>
> and the plot would look like a plot from 0 to 100, with a "+10100"
> rendered
zoom is the other 10%. "No tool" is what I want pretty much 0% of the
time (is there some use for no-tool mode that I'm missing?)
--bb
On 7/31/06, John Hunter <[EMAIL PROTECTED]> wrote:
> >>>>> "Bill" == Bill Baxter <[EMAIL PROTECTED]> writ
On 7/31/06, Ken McIvor <[EMAIL PROTECTED]> wrote:
> On Jul 30, 2006, at 8:07 AM, Bill Baxter wrote:
> > I went ahead and implemented this yesterday on a long plane flight.
> > The changed files (backend_bases.py, and widgets.py) are attached to
> > the above tra
Hi Ken,
Thanks for the reply.
On 7/31/06, Ken McIvor <[EMAIL PROTECTED]> wrote:
> On Jul 24, 2006, at 9:16 PM, Bill Baxter wrote:
> > I think all these problems could be fixed if the display interface
> > were turned into a separate process that communicates with the Pyt
On 7/30/06, Andrew Straw <[EMAIL PROTECTED]> wrote:
> The basic
> idea is to create a layout engine for matplotlib. Not wanting to
> (re-)invent an API, I decided simply to imitate the layout engine I knew
> best, which is wxPython.
Very cool!
Matplotlib is quite nice, but I keep running into problems with the
actual display interface.
In some cases the plot window freezes and such when using it from a
debugger, or sometimes pylab.show() just never returns. Matlab's
plotting interface just never gave me so much trouble.
I think all the
ime to implement it (though it
seems like it would be a fun project if I did have the time).
I am curious as to what the current thinking is about tacking such
event loop issues, though. Surely folks don't think that "use
ipython" is the be-all-and-end-all ultimate solution.
-
Matplotlib is quite nice, but I keep running into problems with the
actual display interface.
In some cases the plot window freezes and such when using it from a
debugger, or sometimes pylab.show() just never returns. Matlab's
plotting interface just never gave me so much trouble.
I think all the
19 matches
Mail list logo
