[GRASS-dev] GRASS7 wish

Michael Barton michael.barton at asu.edu
Fri Jun 16 02:05:30 EDT 2006


Something like this was suggested in the GUI roadmap discussions last fall
and winter. It will make upkeep easier in the long run.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: David Finlayson <david.p.finlayson at gmail.com>
> Date: Thu, 15 Jun 2006 10:12:34 -0700
> To: GRASS developers list <grass-dev at grass.itc.it>
> Subject: [GRASS-dev] GRASS7 wish
> 
> As part of my Pythonification of grass project, I'd like to add to our
> GRASS 7 workload:
> 
> Would it be useful to have metadata about our scripts and programs?
> Basically, what I propose is a simple text file that describes each
> command and script in a standard format. I like the format that
> g.parser uses in sh scripts today. I would extend it to include a
> short help and long help description and a sort-of 'magic cookie'
> which describes how to launch the script/program.
> 
> g.parser would be adjusted to read the resource file so there would be
> no user-visible changes. HTML documentation would be built using the
> resource file and an HTML template. GUI's could build their GUI code
> based on the resource file.
> 
> The format should be quick and easy so that script coders can add a
> resource file for their program with a minimum of fuss. (Copy and
> paste a template from the wiki for example).
> 
> What do you think?
> 
> -- 
> David Finlayson
> 
> 




More information about the grass-dev mailing list