[GRASS-dev] gis.m improvements

[Hamish]

> But r.what reads the WIND file. If its coordinate input is outside the
> extents listed in the file, it gives an error. V.what does NOT worry
> about the WIND file and will query any coordinates you give it.
> 
> It seems that r.what needs to be modified so as to not worry about the
> extents in the WIND file. I don't see an easy work around for this
> (beyond setting the region with g.region). We really don't want to
> have the map displays mess with the WIND file.

The default behaviour of r.what can't change. All raster modules have to
respect MASK and regions the same way. (e.g. setting the region can be
used as a cheap de facto MASK in scripts) However a flag could be added
to r.what to test vs. the raster's window instead of the region's. I
expect doing this could be problematic.


> What to call "settings"
..
> Workspace: 1
> Settings:
> Layers:
> Groups:
> Other (offer name and justification):

"settings" is too generic. Can I change the display font there? the
default database? I think "workspace" makes good sense. layers and
groups, no.

call layers in the GUI "display layers"? "graphical layers"?


> > 10. I really think that some layer options (especially
> > for vectors) should be grouped using tabs, like:
> > 
> > Symbology|Labels|Queries|Misc
> 
> Probably a good idea, though this is most relevant to vectors,
> thematic layers, and may vector chart layers. The others are so short
> that this is not worth it. However, it would also take some serious
> rewriting of the option panel code. I'm trying to get all this
> stabilized so we can have a 6.2 feature freeze.

This seems like a good point to look into the vector GUI controls. They
are way too complex and overwhelming for a new user. Your first day
flying a plane and you're given a 747 cockpit of options..
Could more obscure controls be put into background "advanced" tabs? or
"area/point/line" themed tabs? (with redundancy, but that's ok)


Hamish