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

GRASS GIS trac at osgeo.org
Wed Mar 19 02:09:58 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:  default   |     Version:  unspecified              
Resolution:            |    Keywords:                           
Comment (by 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.

 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.

 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 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.


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

More information about the grass-dev mailing list