On 05/04/13 08:23, Anna Kratochvílová wrote:
And what should the custom gui look like? It should probably provide all the options but better organized (e.g. symbology containing symbols, colors, lines...) and some less important features should be hidden (collapsible pane).
AFAIU Hamish' suggestion, the idea is not to create _one_ dedicated GUI for d.vect, but rather to create several simplified GUIs which cater to specific usages of d.vect. To take his example of d.varea, you could have a GUI for displaying vector areas where the only options visible are those pertinent for displaying areas (so no symbols for example), where type=area is pre-chosen (and invisible), etc. A bit in the line of the QGIS GRASS toolbox, but only for d.vect.
Should there be also a dedicated gui for d.rast? I don't like the possible inconsistency here.
d.rast is not nearly as feature-filled as d.vect, so I don't really see the need.
In any case the full d.vect module GUI has to stay available as well. Moritz _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
