#2136: Create standard options for map or file base name (prefix)
-----------------------------------------+----------------------------------
 Reporter:  wenzeslaus                   |       Owner:  grass-dev@…            
  
     Type:  defect                       |      Status:  new                    
  
 Priority:  normal                       |   Milestone:  7.0.0                  
  
Component:  Parser                       |     Version:  svn-releasebranch64    
  
 Keywords:  base name, prefix, basename  |    Platform:  All                    
  
      Cpu:  All                          |  
-----------------------------------------+----------------------------------

Comment(by wenzeslaus):

 {{{
 module->overwrite = 1;
 }}}

 [http://grass.osgeo.org/programming7/structGModule.html GModule] overwrite
 solves only one of the problems. It adds the overwrite flag and even GUI
 respects it this is great. But it does not standardize the option name
 (key), label and description.

 So, r58311 and [source:grass/trunk/raster/r.mapcalc/main.c#L114 L114] in
 `r.mapcalc` solves the main problem for now but still leave here the
 confusion (see [http://lists.osgeo.org/pipermail/grass-
 dev/2013-November/066402.html GRASS-dev i.pca doesn't have the '--o'
 flag]).

 Moreover, documentation to the standard option would define if underscore,
 dot or nothing is used to separate basename/prefix from the suffix/result
 name. So, user would know what to expect and programmer what to implement.

 Finally, I hope that in future, parser, GUI or both will use the
 information from (or defined by) standard flag to provide some checking
 (such as validity of name as map name) or some additional functionality
 (such a visual warning in GUI if maps with the same basename/prefix
 already exists).

 Anyway, thank you for the fix for `i.pca` and `r.texture`.

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

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to