matplotlib-devel Mailing List for matplotlib

Charles Moad wrote:
> 	In learning matplotlib's backend API I played around in starting a
> Quartz image backend. FWIW I am posting this if anyone wants to have a
> look. I made a quick page on my wiki:
> 
> http://euclid.uits.iupui.edu/wiki/index.php/Matplotlib
The last time I looked at the Apple-provided wrappers, I found them to 
be inadequate for drawing stuff. If I remember correctly, some of the 
arguments require arrays of <Foo>, but they never wrote the typemaps to 
convert Python lists of <Foo> to the appropriate <FooPtr>. Worse, 
there's no source or documentation; you have to fly blind with the 
SWIGged API.
So I wrote ABCGI (A Better CoreGraphics Interface; I'm uncreative). It's 
part of Enthought's Kiva, but it could be trivially ripped out to stand 
alone.
http://svn.enthought.com/svn/enthought/branches/converge/kiva/mac/
It's more complete than the Apple wrappers, and plays nicely with 
Numeric. It would need some numerixifying to play nicely with 
matplotlib, probably. It plays nicely with PyObjC and PIL, too.
-- 
Robert Kern
rk...@uc...
"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
 -- Richard Harter

>>>>> "Charles" == Charles Moad <cm...@in...> writes:
 Charles> 	In learning matplotlib's backend API I played around
 Charles> in starting a Quartz image backend. FWIW I am posting
 Charles> this if anyone wants to have a look. I made a quick page
 Charles> on my wiki:
 Charles> http://euclid.uits.iupui.edu/wiki/index.php/Matplotlib
Hey Charles,
It was good to meet you at scipy -- thanks for putting this up.
 Charles> 	I am probably more interested in starting a PyObjC
 Charles> backend to provide interactive and agg options as well.
 Charles> Is this something that should wait for the backend
 Charles> refactoring???
I think you should proceed with this. The GUI stuff is independent of
the backend rendering, so will work regardless. You might take a look
at the gtk backend as a guide, which is the most modular in the sense
that you can reuse the gtk GUI components with Cairo, Agg or native
GDK rendering. Also, if you incorporate agg rendering, you'll be
insulated from any backend changes, since agg will handle the drawing.
Finally, if you want to use native rendering which I think you should
since you've already gotten a good start, it will be an easy port in
any case since most of the issues will be the same whichever final
backend API we settle on.
JDH

	In learning matplotlib's backend API I played around in starting a
Quartz image backend. FWIW I am posting this if anyone wants to have a
look. I made a quick page on my wiki:
http://euclid.uits.iupui.edu/wiki/index.php/Matplotlib
	I am probably more interested in starting a PyObjC backend to provide
interactive and agg options as well. Is this something that should wait
for the backend refactoring???
- Charlie