Darren Dale wrote:
Hi Eric,
On Thursday 19 July 2007 02:10:03 pm Eric Firing wrote:
unless John or someone else
contradicts me I request that you restore the original numerix, or
something like it, so that users' external code can still use numerix to
deal with Numeric and/or numarray code
On Thursday 19 July 2007 02:26:05 pm John Hunter wrote:
On 7/19/07, Darren Dale [EMAIL PROTECTED] wrote
On Thursday 19 July 2007 01:18:21 pm John Hunter wrote:
I have not been able to install traits by following the instructions in
mtraits.py.
[...]
I encountered a similar problem at
Darren Dale wrote:
On Thursday 19 July 2007 02:26:05 pm John Hunter wrote:
On 7/19/07, Darren Dale [EMAIL PROTECTED] wrote
On Thursday 19 July 2007 01:18:21 pm John Hunter wrote:
I have not been able to install traits by following the instructions in
mtraits.py.
[...]
I encountered a
On 7/19/07, Eric Firing [EMAIL PROTECTED] wrote:
The instructions still say to check out traits 2.0, but Robert is
recommending that we go with traits 3. Do you really want to stick with
version 2 now?
No, I'm happy to move over. But I spent way more time getting traits
working and
John Hunter wrote:
On 7/19/07, Eric Firing [EMAIL PROTECTED] wrote:
The instructions still say to check out traits 2.0, but Robert is
recommending that we go with traits 3. Do you really want to stick with
version 2 now?
No, I'm happy to move over. But I spent way more time getting
Probably a better question for the help list, but has anybody written
an artist that can display a semi-infinite or infinite line?
axvline and axhline can fake it for vertical and horizontal infinite lines,
but they cannot handle slopes or semi-infinite lines.
Thanks,
- Paul
On Jul 19, 2007, at 12:28 PM, Fernando Perez wrote:
Is Peter Wang on this list? If not, perhaps you should CC him and tip
him to come over. I know Robert monitors this, but we shouldn't make
him the single point of responsibility for keeping tabs on the bridges
with Chaco/ETS.
Actually I
Somehow I accidentally deleted a line in a part I thought I hadn't touched.
It's a two line change, so I'll just tell you what to change:
Find the line:
set_clipbox_rasterizer(gc.cliprect);
in src/_backend_agg.cpp in the draw_lines function. (around line 1500)
Right after it, add the
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 my major
On Jul 19, 2007, at 3:05 PM, Bill Baxter wrote:
Chaco may be formidable and complex, but so is the list of features
and requirements you just posted. What about just focusing on a Pylab
wrapper for Chaco? And working with Peter to make Chaco everything
you envison. Or does Chaco have the
On Thursday 19 July 2007 04:05:11 pm [EMAIL PROTECTED] wrote:
Somehow I accidentally deleted a line in a part I thought I hadn't touched.
It's a two line change, so I'll just tell you what to change:
Find the line:
set_clipbox_rasterizer(gc.cliprect);
in src/_backend_agg.cpp in the
On 7/19/07, Christopher Barker [EMAIL PROTECTED] wrote:
This is potentially a major win, because we currently
move the data around on every draw.
Is it that expensive to push data around? In any case, it does sound
cleaner and more efficient not to.
It can be very expensive. Imagine you
On 7/19/07, Eric Firing [EMAIL PROTECTED] wrote:
Please let me know if you are still online (I know it is very late in
Germany); otherwise I may have to revert your changes until the problems
are fixed.
Eric, since it looks like you have not reverted these changes, I went
ahead and did so
(oops, I meant to send that to the matplotlib list)
Hi,
I was looking at the transform code recently..
On Thu, July 19, 2007 7:31 pm, John Hunter wrote:
The potential cost is not in the 3x3 vs 4x4, but in the extra row of
junk data you would store in the data matrix, which is N extra values
John Hunter wrote:
Do we want to use 3x3 or 4x4 to leave the door open for 3D developers?
4X4 -- is there much cost?
The potential cost is not in the 3x3 vs 4x4, but in the extra row of
junk data you would store in the data matrix, which is N extra values
for plotting N points . The
On Thu, Jul 19, 2007 at 03:31:26PM -0700, Christopher Barker wrote:
In matplotlib, the plot functions are matplotlib.axes.Axes methods and
I think there is consensus that this is a poor design.
Well, the OO interface has always felt a bit clunky to me, but I'm not
sure where else plot
On Thursday 19 July 2007 8:02:53 pm Fernando Perez wrote:
- Consider a file called mpl.conf:
# Top-level
backend = TkAgg
interactive = False
# Things that can only be set at init time, they become read-only
afterwards
[InitOnly]
numerix = numpy
[...]
- Then, consider the following bit
Wow, lots of food for thought. Thanks John!
On Jul 19, 2007, at 12:18 PM, John Hunter wrote:
= Objects that talk to the backend primitives =
Have just a few, fairly rich obects, that the backends need to
understand. Clear candidates are a Path, Text and Image, but despite
their names, don't
18 matches
Mail list logo
