#102: new tabs in GUI have required last
-----------------------+----------------------------------------------------
Reporter: cmbarton | Owner: [email protected]
Type: defect | Status: new
Priority: major | Milestone: 6.3.0
Component: Python | Version: unspecified
Resolution: | Keywords: wxGUI
-----------------------+----------------------------------------------------
Comment (by martinl):
From grass-dev ML:
2008/3/20, Michael Barton <[EMAIL PROTECTED]>:
> There is no need for the CLI and GUI to be consistent with respect to
> options ordering. For the CLI, option order is irrelevant; options
> can be typed in any order.
I don't think so, there is no reason to leave CLI and GUI syntax
description inconsistent. The order of parameters should be logical. Yes,
you can type them in order whatever you like, the point here is module
usage description, e.g. v.in.ascii
input -> tab 'Required'
output -> tab 'Required'
fs -> not defined (tab 'Optional')
skip ->not defined (tab 'Optional')
columns -> tab 'Columns'
x > tab 'Columns'
y -> tab 'Columns'
z -> tab 'Columns'
cat -> tab 'Columns'
and some flags ...
> For the GUI option order is very important because the user must
> access the options only in the order presented by the GUI. Thus we
> need to make sure the options order in the GUI section is the most
> logical and useable for the GUI. This section has no impact at all on
> the CLI.
yes, anyway I think the order of parameters given to G_parser() should be
logical and be grouped by guisection identifier.
Martin
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/102#comment:5>
GRASS GIS <http://grass.osgeo.org>
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
