The polar demo in examples/polar_demo.py no longer displays the spiral
and axes. It worked a couple of weeks ago when I was testing the contains()
method.
I downloaded a fresh build of matplotlib pulled from svn today. Tested on
python 2.5 OS X. Should be on the wxAgg backend, though I don't
I've been working on a laboratory in which we can fruitfully discuss,
test, implement mpl1 design issues. I am a big fan of
python-as-modeling-language approach to design. I have tried to solve
from the ground up some of the design flaws in matplotlib -- the
transformation architecture and the d
On 7/19/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
Norbert,
In addition to the problem that numerix was supposed to retain support
for Numeric and numarray for the time being, for external use, there is
the problem that all examples are currently broken.
Please let me know if you are still online (I know it is very late in
Germany); otherwise
Norbert,
Cancel my last message. I panicked. It looks like the problem with my
attempt to run backend_driver.py was that your changes required deletion
of the build directory and/or previous matplotlib installation; after
doing that, backend_driver.py runs.
The comment about numerix is still
Hi John,
On Thursday 19 July 2007 01:18:21 pm John Hunter wrote:
> I've been working on a laboratory in which we can fruitfully discuss,
> test, implement mpl1 design issues.
[...]
> You will need the latest svn matplotlib and
> the latest svn enthought traits 2 -- see the header of mpl1/mtraits.
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. easy_install is pulling in enthought.util-3.0a1, which conflicts
> with enthought.resource-2.0b1. Why
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 and arrays.
I tho
On Thu, Jul 19, 2007 at 01:26:05PM -0500, 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. easy_install is pulling in en
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 num
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
Darren Dale wrote:
[...]
>> The point is that although users will have to *have* numpy, they will
>> not yet have to convert all their other packages to numpy; if they have
>> extension packages built on numarray, for example, and accessed via code
>> using matplotlib.numerix, everything will still
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.
> [...]
>
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 inst
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 g
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
---
That seems to have to do with the line culling agg patch I sent. I never
thought to check with polar plots. I'll look into it.
Allan
On Thu, July 19, 2007 12:17 pm, Paul Kienzle wrote:
> The polar demo in examples/polar_demo.py no longer displays the spiral
> and axes. It worked a couple of wee
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
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 following
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
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 th
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
Lots of god stuff John!
> There is also the question of whether
> we want to pay up and use 4x4 from the ground up and just ignore the
> 3rd dimension to open the door for 3D support.
I say yes! 3-d really is a very often needed and requested feature.
Sure, we can go to VTK or something for re
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. Imagi
On Thursday 19 July 2007 6:31:26 pm Christopher Barker wrote:
> > There is also the question of whether
> > we want to pay up and use 4x4 from the ground up and just ignore the
> > 3rd dimension to open the door for 3D support.
>
> I say yes! 3-d really is a very often needed and requested feature.
On Thursday 19 July 2007 7:31:11 pm John Hunter wrote:
> On 7/19/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> > How many back-ends does the future hold? It seems if the GUI toolkits
> > all use *Agg, then that's only one render for all of them. Then we need:
> >
> > SVG
> > PDF
> > PS
> > Ca
On 7/18/07, Brian Granger <[EMAIL PROTECTED]> wrote:
> > 3. Traits. We (Brian and I) have gone back and forth a lot on Traits,
> > and we've come very close to just making them a dependency. The only
> > real issue holding us back is that ipython so far has exactly *zero*
> > extension code, whi
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 . T
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 pl
On Thu, Jul 19, 2007 at 12:18:21PM -0500, John Hunter wrote:
> = Z-ordering, containers, etc =
>
> Peter has been doing a lot of nice work on z-order and layers for
> chaco, stuff that looks really useful for picking, interaction, etc...
> We should look at this approach, and think carefully about
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 f
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'
On Thu, Jul 19, 2007 at 10:42:56PM -0500, Ken McIvor wrote:
> >= Traits =
> >I think we should make a major committment to traits and use them from
> >the ground up. Even without the UI stuff, they add plenty to make
> >them worthwhile, especially the validation and notification features.
> Code
Hi,
I cannot install matplotlib from latest svn.
error: package directory 'lib/matplotlib/numerix/mlab' does not exist
Nils
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 200
36 matches
Mail list logo
