Opened 9 years ago

Last modified 8 months ago

#1075 new enhancement

Better default values in GUI function

Reported by: vesnikos Owned by: grass-dev@…
Priority: minor Milestone: 7.6.2
Component: wxGUI Version: svn-trunk
Keywords: forms, module defaults Cc:
CPU: All Platform: All

Description

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

Change History (9)

comment:1 in reply to:  description Changed 5 years ago by wenzeslaus

Keywords: forms module defaults added

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

comment:2 Changed 4 years ago by martinl

Milestone: 7.0.07.0.5

comment:3 Changed 3 years ago by martinl

Milestone: 7.0.57.3.0

comment:4 Changed 3 years ago by martinl

Milestone: 7.3.07.4.0

Milestone renamed

comment:5 Changed 22 months ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:6 Changed 17 months ago by neteler

Milestone: 7.4.17.4.2

comment:7 Changed 14 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:8 Changed 10 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:9 Changed 8 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.