[GRASS-dev] Re: [GRASS GIS] #102: new tabs in GUI have required last

GRASS GIS trac at osgeo.org
Wed Mar 19 06:29:11 EDT 2008

#102: new tabs in GUI have required last
  Reporter:  cmbarton  |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect    |      Status:  new                      
  Priority:  major     |   Milestone:  6.3.0                    
 Component:  Python    |     Version:  unspecified              
Resolution:            |    Keywords:  wxGUI                    
Comment (by martinl):

 Replying to [comment:1 hamish]:
 > FWIW I don't really see the point in putting options in a Required tab
 using the guisection control. That info is already supplied by the
 opt->required parser switch.

 Yes, that's true. But there are some exceptions like r.in/out.gdal,
 v.in/out.ogr where naturally required parameters (input, output) are not
 marked as required. Mainly because of 'list' flag. Otherwise you would
 have to type

 r.in.gdal in=dummy -f

 instead of

 r.in.gdal -f

 which is a bit ugly. For GUI dialog it could be for user a bit confusing,
 to launch r.in.gdal and to find input and output option in 'Optional' tab,
 even dialog for importing raster file into GRASS without 'Required' tab.

 > I'm not completely sold on putting all parser required options in the
 front tab. I would be happy if those options were just bolded.
 > (I can see the problem with something like d.vect where you would have
 to hunt for them in lots of tabs, annoying)
 > For r.colors, v.in.ascii the input can come from stdin which is why
 those input filenames are not required by the parser, although piping to
 stdin isn't really an option from a GUI window.

 Maybe we could rename 'Required' tab to 'Main' tab, bolded required option
 (option->required = YES) and move here few options like in the case of

 > I am not sure about the wxPython GUI but for the TclTk one IIRC tabs are
 created in the order their options arrive, with flags having the first
 pass, and all sorts of other funny rules. I

 It should be same for wxPython, just 'Required' tab is always first and
 'Optional' (i.e. parameter without guisection) the second.

 > think it is bad policy to do a lot of option reordering to make the tabs
 look nice. IMO they should be grouped in logical order when viewed
 serially from the help page. Special care must be taken with the first
 option as users may expect it to be the optional "opt=" from the command
 line.   see trac task #88.

 I agree (CLI and GUI should be consistent here).


Ticket URL: <http://trac.osgeo.org/grass/ticket/102#comment:3>
GRASS GIS <http://grass.osgeo.org>
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/

More information about the grass-dev mailing list