[GRASS5] RE: [bug #4140] (grass) Nviz doesn't start either from GUI or CLI

[benducke at compuserve.de]

I am in favour of having a single module,
something like g.setup that allows the user
to change all sorts of settings related to
GUI-driven things:
 
menu fonts
console fonts
GUI colours
animation codecs
...
 
The settings could then be exported to env vars
and be respected by all GUIs, such as gis.m,
the runtime forms and NVIZ.

 

> Von: Hamish <hamish_nospam at yahoo.com>
> Datum: Donnerstag, 16. März 2006 2:36 am
> Betreff: Re: [GRASS5] RE: [bug #4140] (grass) Nviz doesn't start 
> eitherfrom GUI or CLI
> 
> > > I dug back into some of my old archives from when I had looked 
> into> > going back to an nviz start-up script. 
> > 
> > what's the advantage of starting from a script? disadvantage?
> > 
> > 
> > The attached patch will change the NVIZ animation encoding codec 
> from> MPEG-1 to the much nicer Xvid. It's a proof of concept hack, but
> > functional. Even with a 5x bitrate the Xvid file size isn't all that
> > much bigger than the MPEG-1 file, but the quality is way better. 
> I 
> > don'tthink the Ogg Theora is working, but I didn't really spend 
> any 
> > time on
> > that. Also I know the Xvid codec has a "cartoon mode", but I 
> couldn't> find where to assert that. It might be useful to try.
> > 
> > I think it's good to give the user the option to use a better 
> codec 
> > thanMPEG-1, either by another Tcl radio button for Xvid or an 
> > arbitrarycodec taken from an environmental variable (or g.gisenv 
> > grass variable)
> > if given.
> > 
> > Which approach do you think is best?
> > 
> > 
> > Hamish
> > 
>