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

GRASS GIS GRASS GIS developer
1

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.

i.e. a GUI frontend to g.gisenv + common env vars

Preferably with error checking. ("foo doesn't exist, are you sure?")

That shouldn't be too hard for someone to write.

Hamish

2

I agree that a configuration GUI of some sort would be much
appreciated--especially by those who don't think that grass is green :wink:

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

From: Hamish <hamish_nospam@yahoo.com>
Date: Thu, 16 Mar 2006 23:04:51 +1300
To: <benducke@compuserve.de>
Cc: grass5 <grass5@grass.itc.it>
Subject: Re: [GRASS5] RE: [bug #4140] (grass) Nviz doesn't start either from
GUI or CLI

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.

i.e. a GUI frontend to g.gisenv + common env vars

Preferably with error checking. ("foo doesn't exist, are you sure?")

That shouldn't be too hard for someone to write.

Hamish