[GRASS-dev] grass + matplotlib on mac osx snow leopard

[Massimo Di Stefano]

Hi, i agree,
i come from matlab too, i find matplotlib a very "special" library to make plot. 
(it has a really wel done "how to make graph" help page and a nice basemap library and more ...)

i'd like the idea to use matplotlib as standard grass tool to make graph.

come nack to the osx issue, i fix it :

i rebuild a fresh matplotlib svn code
the only problem i had is about png (lib and include files are not found)
to fix it i did a simlink from the UnixIO framework to usr/local :

sudo ln -s /Library/Frameworks/UnixImageIO.framework/unix/lib/libpng.dylib /usr/local/lib
sudo ln -s /Library/Frameworks/UnixImageIO.framework/unix/include/png.h /usr/local/include     
sudo ln -s /Library/Frameworks/UnixImageIO.framework/unix/include/pngconf.h  /usr/local/include

i don't know how/if can i avoid the sim-link .. but now it works :-)

a problem i'm having now, is about the wx module gui (maybe i need to use a more recent wx-python version)
beacouse the "save to file" prompt give me an "open file" prompt instead, see :

http://www.geofemengineering.it/data/r.ipso_save_file_prompt.png 


regards,

Massimo.


Il giorno 09/feb/2010, alle ore 10.26, Hamish ha scritto:

> Michael wrote:
>> I installed matplotlib awhile back to
>> test it (Leopard). It is quite nice and very versatile. I
>> thought it could be a very nice addition.
> 
> FWIW I'm already quite familiar with Matlab plotting (I use it almost
> every day), so matplotlib (which is more or less a clone of that) would
> be very natural for me to use. That shouldn't count for much, but I
> expect I'm not alone.
> 
>> However, there were objections to another dependency and the suggestion
>> that we should build our own graphing library. But this hasn't happened
>> yet.
> 
> I think it all depends on the level of how much we are going to use it,
> and what doors it opens. If all we need to do is create a line graph it
> is probably easier to write our own. But if we want to replace d.histogram
> etc. with something more fancy, and other R-like goodness we haven't
> thought of yet, I don't see much point in spending a large effort in
> reinventing the wheel for something far from our primary business.
> 
> As matplotlib is a close colleague of numpy (which we already use for the
> wxProfile tool), I don't think it is going too much further to request
> numpy+matplotlib instead of just numpy. Find the packages for one, you'll
> probably find the packages for both.
> 
> 
> 2c,
> Hamish
> 
> 
> 
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev