[GRASSLIST:2640] Re: d.his-d.shadedmap manual inconsistencies

[cmbarton]

I'm just starting to use GRASS, but have used other GIS systems quite a 
bit. I appreciate the opportunity to have input to the next version of 
the (very nice BTW) user interface.

On Thursday, November 8, 2001, at 10:36 AM, Glynn Clements wrote:

> 1. Should the menu entries be changed to call d.his rather than
> d.shadedmap? The latter doesn't exist outside of tcltkgrass, and has
> no manual page or help file.
>
> 2. Or should d.his just be renamed to d.shadedmap? d.his is something
> of a misnomer; it doesn't actually correspond to what is normally
> meant by "HIS" (aka "HSV", "HSB").

Option #2 seems the best in the long run. However, I don't know how much 
this would affect people who have scripted d.his. You might want to keep 
the name d.his with links to the new command d.shadedmap to maintain 
backward compatibility as a number of unix commands do.

>
> 3. Presumably there should be a menu entry for r.his (and r.composite,
> and anything else which has been added recently).

Yes. Although I wouldn't want to drop the command-line option, it would 
be very nice to have every command in the menu structure. For one thing, 
it is easier to get a quick idea of what is possible that way.

>
> 4. Is the syntax for r.his (separate options for the R/G/B output
> layers) sensible? Or should there be a single option for the "base"
> name, to which ".r", ".g" and ".b" are appended?
>

The last option appeals to me, though I haven't used this module and so 
can't speak from experience, and is consistent with other programs which 
produce multiple related files as output.

I don't know if  you are the one to ask, but I saw a nice screen shot of 
GRASS running in the Mac OS X Aqua interface. Do you know if this is 
still under development and how it is coming.

Michael Barton, Professor & Curator
Department of Anthropology
Arizona State University
Tempe, AZ  85287-2402
USA