[GRASS-dev] t*. modules

[Helena Mitasova]

yes, this needs to be discussed.

My first reaction was let us keep just one letter but after thinking about Soeren's argument,
and checking the current names  t., tr., tv., as Soeren suggests makes better sense,
especially given that we already have db.* and ps.* commands.

Are there any other suggestions how to handle this? 

The best is to look here at the first set of commands
http://trac.osgeo.org/grass/browser/grass/trunk/temporal
For example we have 
t.list type=rast
tr.list input=myrasterseries
How would these be handled using a different naming convention?



Helena 

On Oct 20, 2011, at 4:38 PM, Martin Landa wrote:

> Hi,
> 
> 2011/10/20 Sören Gebbert <soerengebbert at googlemail.com>:
>> So i would like to keep t.*, tr.*, tv.* and tr3.* as prefix to simply
>> identify the new datatypes, extending the common r.*, v.* and r3.*
>> prefixes with a "t".
> 
> historically there are prefixes like g., r., v. or r3. From this point
> of view it would be good to keep spatio-temporal functionality under
> one prefix. It's just introducing to many new prefix compared to the
> number of existing prefixes. Just my personal opinion. I would like to
> open discussion to avoid renaming of modules later in the future. We
> need to make decision in early stage of development.
> 
> Martin
> --
> Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev