Hi, Anna and I discussed the GUI sections of g.list and g.remove. The changes are now in trunk (r62248). However, few issues still remain.
It seems to us that although `names` and `ignore` in g.remove are similar from the point of view of implementation, they have completely different use case. While `names` is here to provide a simple interface, `ignore` extends the interface which is using patterns. So, non-advanced user using GUI will surely want `names` but not `ignore` and GUI should reflect this. Thus `ignore` should probably go to Pattern (although it is not 100% consistent) and `names` to some basic category. Also, Required section (of both g.remove and g.list) contains just one item - `type`. In case of g.remove, it could make sense to have the `names` together with `type` in some Basic section which would be the primary section users can focus on (besides approval by -f in Optional). This of course expects that no elements will be added to the `type` list (#2440, #2437). So, the big question is if we want to allow Required section to be overridden by another section if it is provided. Currently if option is required, GUI puts it into Required section no matter if another GUI section was specified. Thanks for your opinions, Vaclav r62248 http://trac.osgeo.org/grass/changeset/62248 #2440 http://trac.osgeo.org/grass/ticket/2440 #2437 http://trac.osgeo.org/grass/ticket/2437
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
