[GRASS-user] Some suggestions

[Hamish]

Michael:
> Having a tear off layer manager for each display would *really* make
> for a cluttered screen. There wouldn't be much reason for the tear off
> manager in this case.

I'm thinking about a dual monitor setup, you have a display window and
associated control window in each. Effectivly concurrent use of the same
mapset. .. just an idea ..


M:
> >> What is missing is a fully interactive terminal--one that will
> >> prompt you for entries and you can respond.
H:
> > Do you mean like:
> >   GRASS_UI_TERM=1 i.landsat.rgb
> > does, but output to tcl/python code not in the xterm?
M:
> No. More like being able to enter g.setproj and answer the prompts.


G63> GRASS_UI_TERM=1 i.landsat.rgb

OPTION:   LANDSAT red channel
     key: red
required: YES

Enter the name of an existing raster file
Enter 'list' for a list of existing raster files
Hit RETURN to cancel request
> 

?


> We can create a full-fledged terminal in wxPython I think. 
..
> If we start using Python big time, however, it could be worth thinking
> about a Python terminal for all. But this is different from a standard
> *nix terminal.

Offering a python terminal is a very nice idea. Then you get access to
all grass commands + SWIG access to the libgis fns in a safe, platform
consistent way.

Maybe package the module families as import r.py, v.py, g.py etc, so
"r.module" links to [r.]r.module. much better than:

import os, popen2
command = 'ls'
child = os.popen(command)
data = child.read()
child.close()

[maybe easier with the subprocess module or something already written
for the wxPyGUI? (no idea about python)]


Hamish