[GRASS-dev] [GRASS GIS] #2042: wxgui: no more menu access to r.in.gdal / v.in.ogr

[GRASS GIS]

#2042: wxgui: no more menu access to r.in.gdal / v.in.ogr
--------------------------------------+-------------------------------------
 Reporter:  mlennert                  |       Owner:  grass-dev@…              
     Type:  defect                    |      Status:  new                      
 Priority:  normal                    |   Milestone:  7.0.0                    
Component:  wxGUI                     |     Version:  svn-trunk                
 Keywords:  r.in.gdal, v.in.ogr, gui  |    Platform:  Unspecified              
      Cpu:  Unspecified               |  
--------------------------------------+-------------------------------------

Comment(by martinl):

 Replying to [comment:5 hamish]:
 > As long at the button is worded correctly and put in an appropriate
 place, it doesn't have to be confusing.

 I am not sure about that. Moreover I can hardly say that the place was
 really appropriate. I would say opposite.

 > Putting it along side as a menu item might be confusing for sure. Typing
 'r.in.gdal --ui' (//are you saying that just 'r.in.gdal' will not cause
 the module GUI to open?) from a command prompt requires prior knowledge of
 the module's name and knowing how to do that. Neither is inherently
 "discoverable" or self-documenting. The --ui trick is hardly widely known
 outside of the development team.

 I can hardly imagine normal user who prefer autogenerated dialog rather
 then more user friendly front-end. Most probably if you prefer
 autogenerated dialog you are advanced user who knows how to lunch a
 command from command line. The easiest think is to document it.

 > see also the cartographic composer's way of launching the ps.map dialog
 from the File menu. It's there if you want/need it, but not likely to
 confuse new users.
 >
 >
 > > Similarly for the other modules which have special frontend, e.g.
 > > i.group. From my personal experience, the user in the class were
 > > very confused when they got different GUI dialog when running
 > > i.group from the menu and command prompt.
 >
 > I would suggest the solution there is different wording titlebar etc
 text in the wizard version. i.e. give them better hints along the way to
 guide their expectations. (easier said than done of course)

 But these dialogs are not "wizards". Since most users will use front-ends
 and they will happily live without knowing about autogenerated dialogs I
 don't feel that we need to show this functionality so much. There must be
 a way how to launch autogenerated dialogs, in the best case the same for
 all commands which have front-ends. From this point of view `--ui` seems
 to be better then putting buttons somewhere. The simple the better. Trying
 to find a sense in launching front-end and from the front-end launching
 autogenerated dialog. How many user will use it and how many of them will
 be simply confused?

 [...]

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2042#comment:7>
GRASS GIS <http://grass.osgeo.org>