#1075: Better default values in GUI function
-------------------------+--------------------------------------------------
Reporter: vesnikos | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: minor | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: | Platform: All
Cpu: All |
-------------------------+--------------------------------------------------
When running a command, the GUI always have some inputs, like name of
dataset, command called and etc..
what Im proposing, is that the gui should recommended (or autofill) some
optional or required fields that the user needs to fill. For example the
proposed name of an output file/layer could be
${input_name)_${command_called}_${region}.
The same can said for some arithmetic values.
The whole idea behind this suggestion is to give the user some peace of
mind with the trivial task, and let him focus on his real objectives.
A second enchantment that is being addressed is that this way important
but usually over looked inputs will be drawn focus upon
#1075: Better default values in GUI function
------------------------------------+---------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: minor | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: forms, module defaults | Platform: All
Cpu: All |
------------------------------------+---------------------------------------
Changes (by wenzeslaus):
* keywords: => forms, module defaults
Comment:
Replying to [ticket:1075 vesnikos]:
> what Im proposing, is that the gui should recommended (or autofill) some
optional or required fields that the user needs to fill. For example the
proposed name of an output file/layer could be
`${input_name)_${command_called}_${region}`.
This makes sense to me. It is probably possible to implement without much
side effects, although that's hard for the code in `forms.py`. Generating
the new name can be a bit tricky: Some modules have more outputs, e.g.
`r.slope.aspect`, so you have to find out, what are the output options and
if there is more then one, include also the name of the option. I'm not
sure about the region, details are part of the map metadata (e.g.
`r.info`). It would be good to think about different cases before
implementing anything like that.
> The same can said for some arithmetic values.
These as well as other defaults should be solved at the level of modules.
If you have some ideas, please suggest them individually for a given
module.