[GRASS-dev] Re: Re: [GRASS GIS] #156: new attribute in Option struct to allow conditional options requirement

[Martin Landa]

Michael,

2008/5/5 Michael Barton <michael.barton at asu.edu>:
>  Why not have one field that defines the order of the tabs and one that
>  defines the tab label? I haven't dug into the TclTk code that parses these,
>  but it can't be that hard to change it to account for this. The same goes
>  for the wxPython parser code. It would probably simplify a LOT of things in
>  the parser.

I am not quite sure here, I think it is not necessary to define order
of tabs in that way. In the best case flags/parameter should be
grouped based on guisection (or logical connection) when defining
Flag/Option instances. See d.vect where flags/parameters are grouped
by guisection. It means to keep some kind of consistency between CLI
module usage description and GUI dialogs (tab order).

BTW, in wxPython code, tabs are reordered ('required' tab is always
the first one [1]).

Martin

[1] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_modules/menuform.py#L853

-- 
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *