[GRASS-dev] [GRASS GIS] #3633: wxGUI: wording of menu entries for data import

GRASS GIS trac at osgeo.org
Wed Nov 28 20:04:14 PST 2018


#3633: wxGUI: wording of menu entries for data import
--------------------------+------------------------------
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.6.0
 Component:  wxGUI        |    Version:  unspecified
Resolution:               |   Keywords:  data import menu
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+------------------------------

Comment (by wenzeslaus):

 Replying to [comment:1 mlennert]:
 > Any opinion on this ?

 I agree that if the wizard is very different from the module, or even
 perhaps when it is a wizard or a more fancy dialog as opposed to the
 generated one, it should not include module name in square brackets.
 (However, mentioning somewhere the name of the module is desired.)

 > Would this still be an option for 7.6 ?

 I think so.

 > Or are menu entry names considered API changes ?

 I don't think so. What this breaks are translations (hopefully fixed
 before the actual release) and tutorials (documentation should be updated
 with the change). I would say that it is nice to keep the strings the same
 or almost the same within a minor version so that tutorials can say
 something like "use with 7.4" or "developed for 7.4". However, easier,
 more intuitive interface outweighs stability of some tutorial somewhere
 (as I said the documentation should be changed together with the string).

 Speaking more generally, the reason why it is not an API change is that
 these are being interpreted by humans doing tutorials or following notes
 who can deal with changes in wording and focus on the meaning instead.

 In GRASS GIS, the issues coming from changes is user visible strings are
 mitigated by the fact that tutorials are often written using commands
 rather than screenshots and menu and dialog navigation. Although these are
 very useful and desired, they are (or can be) only additional material.

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



More information about the grass-dev mailing list