[GRASS-user] grass70 and display monitor

[Vincent Bain]

Thank you for your answers and advices.

Glynn, with your method based on displaying grass files on the fly in a
viewer, I guess all d.* interactive commands will fail, won't they ?

Deep down I want to know how much I will have to adapt some shell
scripts I wrote for grass6* when my users migrate to grass70.

My feeling on this point with care for durability of the application -
and I think grass is mostly used by people in search of customization -
is it would be nice that be maintained these fundamentals... To my mind
it is one of the most important benefits of open source apps. On the
other hand I am not aware enough of the constraints that lead to drop x
monitors.

Bye,
Vincent


Le jeudi 03 décembre 2009 à 06:00 +0000, Glynn Clements a écrit :
> Vincent Bain wrote:
> 
> > my question could be insane but I am wondering if there is an equivalent
> > command to d.mon in grass70.
> > In several man pages I saw a reference to d.frame but it seems not be
> > implemented yet.
> > 
> > Or will grass70 give up with x monitors ? considering one still can
> > launch grass in text mode, I guess there might be a way to open a
> > graphical device.
> 
> GRASS 7.0 does not support monitors. The various display "drivers" are
> libraries against which the display library is linked. There are no
> persistent monitor processes as in 6.x, meaning that there is no
> persistence of state between d.* commands, so no d.frame, d.font etc.
> 
> All rendering parameters are set via environment variables. Some of
> these are listed in the "variables" manual page, while others are
> listed in the manual pages for the various drivers.
> 
> You can approximate the pre-7.0 workflow using an image viewer which
> automatically refreshes the display whenever the file changes. For X,
> you can use the ximgview program, e.g.:
> 
> 	export GRASS_PNGFILE=map.bmp
> 	d.erase
> 	ximgview &
> 	export GRASS_PNG_MAPPED=TRUE
> 	export GRASS_PNG_READ=TRUE
> 	# more d.* commands
>