[GRASS-dev] Re: name of nviz_cmd module

[Hamish]

Hamish:
> >> perhaps
> >> 
> >> d.nviz -> d.nviz.script
> >> nviz_cmd -> d.nviz.image

Michael wrote:
> I'd go with d.nviz.image because the
> result of the command is an image, not a script.

I meant d.nviz.script for a (wxPy) replacement of the existing
d.nviz module, which currently creates a tcl/tk script to run in
tcl/tk NVIZ to automatically set up the keyframe animation to
follow a certain camera track, from input coords (eg exported
vector map) or by interactively clicking the display monitor
(grass 6.x only).

a d.nviz.script could call d.nviz.image many times, once for
each timestep.


Hamish

---
GRASS6> d.nviz --help
[...]
Description:
 Creates fly-through script to run in NVIZ.

Flags:
  -i   Interactively select route
  -f   Full render -- Save images
  -c   Fly at constant elevation (ht)
  -k   Include command in the script to output a KeyFrame file
  -o   Render images off-screen
  -e   Enable vector and sites drawing

Parameters:
   input   Name of input raster map
  output   Name of output script
    name   Prefix of output images (default = NVIZ)
   route   Route coordinates (east,north)
    dist   Camera layback distance (in map units)
      ht   Camera height above terrain
  frames   Number of frames
   start   Start frame number (default=0)