[GRASS-dev] moving database commands

Does anyone have any objection to moving all database commands under the
database menu?

In reality, all our database management is related to vector attribute
tables ultimately (at least in the great majority of cases). So this can be
assumed rather than explicitly including some under vector and others under
database.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

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

Michael Barton wrote:

Does anyone have any objection to moving all database commands under
the database menu?

In reality, all our database management is related to vector attribute
tables ultimately (at least in the great majority of cases). So this
can be assumed rather than explicitly including some under vector and
others under database.

we already have an Imagery menu item, which is for all but name raster
modules, so the precedent is already set.

but no opinion really,

Hamish