[GRASS-dev] No Required GUI section for g.list and g.remove

Moritz Lennert mlennert at club.worldonline.be
Tue Oct 14 01:06:43 PDT 2014

On 14/10/14 09:14, Paulo van Breugel wrote:
> Putting the 'ignore' option in  separate tab with patterns is fine I
> think. Also, for g.remove to have the 'type' and 'name' together in one
> tab is also a good idea imho.
> I am not sure I understand the last question; you mean to add the
> possibility to make an option required but still have the option to put
> it in another section? I think that would be a good idea, not only in
> this case, but more in general, it would make it easier to create an
> consistent interface for modules that require more than a few inputs.
> It might be a good idea to flag options as required, e.g., by adding
> '(required)' after the option name?

I'm not sure I agree with this as this would leave the door open for 
required flags to be disseminated across several sections. I like the 
fact that the use immediately sees what is required to run the module.


More information about the grass-dev mailing list