[GRASS-dev] Re: [GRASS-user] Re: grassuser Digest, Vol 9, Issue 1

[Michael Barton]

I very much agree. In order for the GUI and its display to work properly, we
must be able to obtain information about the current region and to change
it. The most transparent way to do this is entirely through the use of GRASS
commands rather than trying to read WIND or other files. Other
information-getting commands that are used in the GUI include r.info,
v.info, r.univar, v.univar.sh, and r.statistics.

I support trying to cleanup and regularize the output of any such commands
that return information about the GRASS environment. But because they are
used currently in the GUI (and other scripts), we need to be careful about
keeping them backward compatible or synching changes with other systems that
depend on them.

Michael


On 1/3/07 1:53 AM, "Paul Kelly" <paul-grass at stjohnspoint.co.uk> wrote:

> So it would be worthwhile I think to look at the existing uses of g.region
> and the matching regexps in gis.m and see if they can be rationalised to
> make best use of the new features of g.region.
> Worth checking throughout the whole source code actually - there are a lot
> of things that call g.region and parse its output. Like I said, definitely
> a good idea to sort out the inconsistencies but need to stay
> backward-compatible until we fix everything that depended on the old
> behaviour.

__________________________________________
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