[GRASS-dev] [GRASS GIS] #2136: Create standard options for map or file base name (prefix)

[GRASS GIS]

#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 zarch):

 Replying to [comment:8 wenzeslaus]:
 > Replying to [comment:6 annakrat]:
 > > Replying to [comment:4 zarch]:
 > > > So maybe in the future the GUI would be able to group maps
 > > > following the rule "basename`__`*" and visualize them in
 > > > the wxGUI Animation or something else...
 > >
 > > I agree with double underscore.
 >
 > I'm not sure about double underscore. I don't like how it
 > looks like. I'm afraid if it will be understandable for users,
 > for example when visualized in some GUI, you don't know how the
 > font will show it (with mono spaced font, you can see two
 > underscores even if they are connected with each other, with
 > other fonts, you don't know). Moreover, so systems can try
 > to interpret the double underscore too (see what Trac did to
 > commit message in r60944).
 >
 > On the other hand, I see the advantages too. It is much harder
 > or more fragile to achieve the same with one underscore
 > (or other character).


 I see two options:
     - avoid to use any separator;
     - choose a "standard" separator for map names;

 I think that define a standard separator could open new possibilities to
 GRASS GUI/interaction. So I believe we should choose one.

 Concerning which separator we should use, personally I've not strong
 opinion about double underscore, my idea is that one underscore is quite
 common in the raster/vector names so I don't think it is a good candidate
 to be used as separator.

 Other options could be:
     - basename:01, basename:02, etc.
     - basename::01, basename::02, etc.
     - basename(01), basename(02), etc.
     - basename[01], basename[02], etc.
     - basename{01}, basename{02}, etc.
     - basename»01, basename»02, etc.


 That became with two ids, like the output of r.tile:
     - basename:00:00, basename:00:01, etc.
     - basename::00::00, basename::00::01, etc.
     - basename(00)(00), basename(00)(01), etc.
     - basename[00][00], basename[00][01], etc.
     - basename{00}{00}, basename{00}{01}, etc.
     - basename»00»00, basename»00»01, etc.

 Using the parenthesis is maybe a little more difficult to parse than just
 a separator and parenthesis are often interpreted by other program, see
 how are rendered here!

 Personally I like the use of a peculiar character like: », ■, or other
 because user should never insert such characters manually and clearly mark
 which maps are automatically generated my GRASS modules, and as far as I
 know they have not particular meaning in other system like shell, trac,
 etc..

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