On 30/01/08 02:39, Michael Barton wrote:
Understood. These python utilities draw to Python canvases, and so normally need the GUI to run. It may be possible for them to output to a graphic file too. But they are designed to work in a GUI environment rather than a command line environment.
http://matplotlib.sourceforge.net/faq.html#BATCHMODE
I don't advocate ditching d.histogram. In fact, the *easiest* thing from my standpoint, would be to have a sophisticated and slick C-graphing module that I just had to call as a command and presto it creates a graphic file that I can pop into a canvas. But I have some understand of the complexity of writing this in C or anything else. That's why to use high level graphing tools to do this.
We do have some C-code which exists. It's just a question of whether we think that someone will take the time for updating that, or whether we should profit of the efforts done for the GUI to just have the same functions also available on the command line (with the additional advantage of consistency). If python is a required dependency anyhow, I don't have any religion about a module absolutely having to be in C if the python version is just as good.
Moritz _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
