matplotlib-devel Mailing List for matplotlib

>>>>> "thane" ==   <th...@ma...> writes:

    thane> I've got an alpha version of a .NET backend up and running
    thane> for matplotlib (http://matplotlib.sourceforge.net/ ).  It
    thane> was just intended to be "proof-of-concept" code, but it
    thane> works.

I'm certainly interested.  I don't know a lot about .Net.  Is your
backend an image backend or GUI one?  If the latter, are you using agg
for rendering ala tkagg, gtkagg, etc, or native .Net drawing?
Inquiring minds want to know.

    thane> This back end is targeted for anyone using PythonNet (see
    thane> http://www.zope.org/Members/Brian/PythonNet/index_html ).
    thane> It should also be compatible with IronPython (see
    thane> http://ironpython.com/) once the standard libraries and
    thane> Numarray (or Numeric) are available for the IronPython
    thane> release.

    thane> If there is any interest, please respond to this post and
    thane> I'll go through the trouble of adding it to the project (at
    thane> this point I don't know how to do this, so any guidance
    thane> here would be appreciated).

The standard procedure for submitting a backend is to send it to the
dev list, where I and other matplotlib developers can take it for a
test drive and submit feedback.

I'd be happy to give it a try.  If you have any extra instructions for
.Net dummies, please send them along with the code.

Cheers!
JDH


 

    thane> --Thane

 

    thane> Thane Plummer, Ph.D.

    thane> CEO Magna Capital, LLC

    thane> (520) 760-4957

    thane> (520) 405-2277 (cell)

    thane>  <mailto:th...@ma...> th...@ma...

    thane>  <http://www.magna-capital.com> www.magna-capital.com

 

 

I've got an alpha version of a .NET backend up and running for matplotlib
(http://matplotlib.sourceforge.net/ ).  It was just intended to be
"proof-of-concept" code, but it works.

 

This back end is targeted for anyone using PythonNet (see
http://www.zope.org/Members/Brian/PythonNet/index_html ).  It should also be
compatible with IronPython (see http://ironpython.com/) once the standard
libraries and Numarray (or Numeric) are available for the IronPython
release.

 

If there is any interest, please respond to this post and I'll go through
the trouble of adding it to the project (at this point I don't know how to
do this, so any guidance here would be appreciated).

 

--Thane

 

Thane Plummer, Ph.D.

CEO Magna Capital, LLC

(520) 760-4957

(520) 405-2277 (cell)

 <mailto:th...@ma...> th...@ma...

 <http://www.magna-capital.com> www.magna-capital.com 

 

 

On Sep 24, 2004, at 10:59 AM, John Hunter wrote:
>
> The other core features that would be nice to have but aren't
> absolutely critical are polar and contour.  I believe the stsci folks
> are working on contour.
>
Off and on, but indeed we are working on implementing contour plots.

Perry

>>>>> "Steve" == Steve Chaplin <ste...@ya...> writes:

    Steve> My argument is that most other software I've looked at does
    Steve> this and it seems to work OK. I guess the reasons are that
    Steve> - it makes software packages smaller - you only need to
    Steve> directly download one copy of a package and do not
    Steve> indirectly download multiple copies of the same package.  -
    Steve> you can end up with multiple versions of a package. And
    Steve> later you may try to recall - which package x did I use to
    Steve> install package y?  - the software package that includes
    Steve> other packages needs to make sure it keeps up to date with
    Steve> with the included packages and does not install old
    Steve> versions.

Hi Steve,

Those are reasonable arguments.  I'm still convinced that it is better
to err on the side of simplifying the install, though.  matplotlib has
been distributing some of it's prereqs for some time (agg, pyparsing)
and not others (Numeric/numarray, freetype, libpng).  I try to balance
the likelihood the user already has the package on their system, the
additional ease/complexity of installation and coding, and package
size.  On balance, I decided to add pytz and dateutil to the
matplotlib src distro - I won't however, overwrite existing installs.

In the past we've included things (fontutils, ttfquery) that were
eventually removed because we found or wrote better replacements.  So
the matplotlib package size tends to fluctuate up and down a bit.
Currently, with src, fonts, icons, examples, example data, and add-on
packages, the src dist comes to 1.6M.  I can live with that.

    Steve> As a way to encourage more users how about working towards
    Steve> moving from the development status of version 0.62.4 "4 -
    Steve> Beta" to 1.0.0 "5 - Production/Stable".  What's the
    Steve> criteria for this step?  My understanding is that it does
    Steve> not mean that all desired features are implemented or
    Steve> complete, it just means that the software is stable, and
    Steve> matplotlib seems to be pretty stable already.

I'm amenable.  Do you know of instances where people aren't using
matplotlib due to it's version number or development status flag?

My working plan is to be mostly 2D feature complete for 1.0, but I am
not wed to this.  As you say, 1.0 really just implies some stability
rather than feature set.

The only thing off the top of my head that must be added before 1.0 is
a Users Guide - I should be done with this already, but alas...
Should be done in a month (I said that last month) I also think it
would also be nice to have a more streamlined, sophisticated configure
process.

The other core features that would be nice to have but aren't
absolutely critical are polar and contour.  I believe the stsci folks
are working on contour.

As for stability, there will probably be a significant refactoring of
the renderer drawing API at some point.  But I don't think this
precludes a 1.0 release.  As long as the matlab interface and OO
Figure/Axes/Text/Line/Patch interface is stable, and it largely is
discussed on the user's list), then I don't think it would break any
existing code to refactor the drawing model down the road.  As far as
I know, noone is directly using the renderer API, and I've never
advertised it.

JDH