v.category problem - was Re: [GRASS-dev] Keywords, help pages...

[Hamish]

> Trevor wrote:
> > All that said, if v.category sacrosanct (although it is unclear to
> > me how this is determined)

All future GRASS 6.x must be backwards compatible with the original
GRASS 6.0.0. We can add things, but not change or remove options. The
idea is that any documentation, books, scripts, apps, data, etc.,
written for GRASS 6 will work on any future GRASS 6. When we switch to
GRASS 7 things can change. This is to provide continuity to the user.

> > the issue remains of how to make things
> > better. Eric Patton has off list offered to improve some of the
> > documentation for v.category based on this discussion. I think
> > however, it would be a good idea to add in Hamish's v.centroids
> > script with help page into the CVS as it provides an obvious and
> > convenient way of doing this for users not deeply familiar with the
> > GRASS 6.x vector modules.

IMO we should do both.

> > I also liked the idea of a v.dissolve
> > script which would make things more convenient and obvious.

Markus wrote:
> I don't see any problems to add those two scripts. The sooner, the
> better :-)

Ok, will do. I'll take care of the tcl menus and 6.2 backporting too.
If someone else wants to write the help page, the help is greatly
appreciated.


One question for the list:

To use "v.add.centroids" or "v.centroids option=add" ? v.add.centroids
is more obvious, but v.centroids leaves the door open for future
options. I have no idea what those options could be, but someone might
think of something. CVS directory removal & above release restrictions
make it a pain to change later.


Hamish