>I propose that we decide once and for all that calling a module by name, >be it in the terminal window, or in the GUI console or via the menu, >launches the actual module GUI.
>If we want to propose specific wizards >to ease the use of these modules, these should be called as such, and >not via the module name. >_That_ causes confusion for many people in my >experience. > And wizards should not be complete replacements of the GUI >modules, but offer specific simplifications or added value (such as the >looping through import calls when importing a directory of files). >IMHO, wizards should always offer a path to the original modules behind >them, in the form of buttons, or at least information. sounds reasonable for me. +1 >- Import wizard for raster maps (with a button to launch the module GUI) >- Import common formats (r.in.gdal) >- Import common formats with reprojection (r.in.import) in terms of the specifications mentioned above, sounds good. +1 ----- best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/relation-between-GRASS-modules-and-GUI-wizards-tp5239780p5239797.html Sent from the Grass - Dev mailing list archive at Nabble.com. _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
