[GRASS-dev] [GRASS GIS] #2409: last call for options keys consolidation

[GRASS GIS]

#2409: last call for options keys consolidation
----------------------------------+-----------------------------------------
 Reporter:  martinl               |       Owner:  grass-dev@…              
     Type:  task                  |      Status:  new                      
 Priority:  blocker               |   Milestone:  7.0.0                    
Component:  Default               |     Version:  unspecified              
 Keywords:  standardized options  |    Platform:  Unspecified              
      Cpu:  Unspecified           |  
----------------------------------+-----------------------------------------

Comment(by wenzeslaus):

 Replying to [comment:99 huhabla]:
 > Replying to [comment:96 martinl]:
 > > Replying to [comment:95 helena]:
 > > > > -1 for voxel, than we could rename 'raster' to 'pixel' ;-)
 > > > >
 > > > > I am still not sure we need to rename than all modules from `r3`
 to `vo`...
 > > >
 > > > so is there also an agreement to rename all r3.* commands to vo.*
 commands and changing all manuals accordingly? If yes, this will require
 several weeks of focused testing and
 > >
 > > not at all, personally I don't like to stick with shortened element
 names (rast, rast3d) just because it makes our life easier. Taking in
 account a real world it seems to me that the reasonable is to rename `rast
 -> raster` and `rast3d -> raster3d` and to modify the parser to understand
 also shortened element names.
 >
 > This would be absolutely my favorite solution.

 I like `raster` and `raster3d`.

 For example, there will be no need to change `grass.script.raster3d`
 (which would end up as `grass.script._3draster` in the other case). From
 this point of view `raster_3d` is also not good because underscore should
 not be in the name of a Python module if possible and moreover I don't
 like `raster_3d` in general. Shortening possibilities are not as important
 to me as name without underscore.

 What about the module names? Are we changing that? Or is `raster3d` just
 `rast3d` in module names?

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2409#comment:102>
GRASS GIS <http://grass.osgeo.org>