[GRASS-dev] Re: grass-dev Digest, Vol 4, Issue 43

Michael Barton michael.barton at asu.edu
Sun Aug 13 01:15:26 EDT 2006


That would certainly make things easier from the GUI standpoint.

In a different vein, what about SVG instead of postscript for output from
d.* commands? Once in a GUI, both TclTk and wxPython can export their
graphic canvases to postscript easily.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: <grass-dev-request at grass.itc.it>
> Reply-To: <grass-dev at grass.itc.it>
> Date: Sun, 13 Aug 2006 06:57:56 +0200
> To: <grass-dev at grass.itc.it>
> Subject: grass-dev Digest, Vol 4, Issue 43
> 
> I'm not entirely sure what you are proposing. The way that I would
> approach it would be to make all of the fundamental GUI operations
> (add/remove/show/hide layers, zoom/pan, etc) available as external
> commands, so you would be able to do e.g. "g.ui add d.rast foo" to add
> a new layer containing the output of "d.rast foo".
> 
> It would be fairly straightforward to modify the raster library so
> that executing a d.* command would send a command to the GUI to add
> that command as a new layer.




More information about the grass-dev mailing list